Skip to content

IDs de agentes derivados de su ejecución — alcance mínimo #2432

Open
13 of 24 issues completed
Open

Description

@mblua

Current selected-file profile delivery

User approved file selectors in Settings and actual session picker, independently remembered per menu, with BASE-hash profile sharing confined to the selected physical file and source-correct launch/restart/restore. The complete seven-phase implementation now has exact author plus four independent approvals. This is the new selected-file cut; historical broad packages and frozen mappings below are preserved, not reactivated.

Canonical: D:/0_repos/AgentsCommander_iac/.ac/plans/2432-selected-file-profiles/plan-v7-selected-file-profiles.md

Plan-SHA256: 2E09A6E856CA77EF70A1C47D9976DB93CF9206C9B0540434199E33FC8821A3BA

Phase Child Class Owner Files Depends SHA256
P01 #2902 design-bearing ac-dev-rust-v5 2 none 4E7F35668B82B21558D89B66D6C2F6B8EA34E1A9832BCC71C38FC91CA2A57542
P02 #2905 design-bearing ac-dev-rust-v5 5 P01 F33B3265428DC8352DA7B37C1792027210691224ADEB64BBA02B324BAFFF2436
P03 #2900 design-bearing ac-dev-rust-v5 5 P02 4C0121088193E18C97DCE1F6F102C84BD4E3C5254AE3105E5D5613FD748DB7AC
P04 #2899 design-bearing ac-dev-rust-v5 4 P03 FBE539FB6C729CD13220918DA161D3A500FE891F7B5098DBDC14CFC4CD9919CB
P05 #2906 design-bearing ac-dev-rust-v5 4 P04 F574CAFCA81660F53CCEAC4877BA27F0D57735F51C92CE3829D58A7A9A16F5C7
P06 #2910 design-bearing ac-dev-webpage-ui-v5 8 P05 0C19AABCAD52A56AA864F5F2476A8E3588A6D8355C1792C225A7488FD3DC7C86
P07 #2911 design-bearing ac-dev-webpage-ui-v5 8 P06 B5F2CFF88818D1E6913874009BDE178A29B9AD0F7B63ABD9326C7ACAA9F2EDDD

Existing native children are intentionally reused only for matching minimum concepts; phase-issues.json in the new plan directory is the authoritative current one-to-one mapping. It does not modify historical certified mappings. #2909 CLI producer work and #2912 minimum docs retain their separate pending reconciliation; unrelated deferred packages remain deferred. No new issue/closed-issue reopening is required. Exact rationale and historical records are preserved in each child.

Standing in-scope consensus authority applies; freeze/current-base/cold gates precede source writes. Execute sequential phase branches/PRs, each closing only its child. Do not close E2432 merely because this selected-file cut lands if other accepted work remains. No final binary/install/release/version change requested.

Exact renewed consensus: room-shared/profile-hash-link-intake/formal-round6-consensus-v1.json. The P01 orphan wire and duplicate-key compatibility decisions are resolved; phase issues, branches, dependencies and file allowlists are unchanged.


Preserved preceding Epic record

Resolución vigente — reverificación de scope mínimo

Objetivo vigente: «los ids de agentes cambien a unos ids que se desprendan de el string univoco que requieren ejecutar». Una ventana/editor. El usuario ordenó atacar únicamente lo estrictamente necesario y revisar el resto después. La auditoría de 22 hijos preserva diferencias entre necesidad conceptual y paquete histórico; no es consenso de implementación. Faltan definir el string/equivalencias y la compatibilidad de IDs anteriores antes de certificar el mínimo exacto. Hash determinista no prueba idempotencia. Las especificaciones y dependencias históricas no habilitan ampliar ni bloquear automáticamente el núcleo reducido. Esta resolución no elimina ni revierte comportamiento entregado; los estados abiertos/cerrados se conservan.

Prioridad de lanzamiento

9 issues contienen conceptos requeridos, con alcance reducido: #2892, #2894, #2897, #2899, #2902, #2908, #2909, #2910 y #2912. No implica nueve implementaciones o fases nuevas: reutilizar trabajo válido y agrupar el mínimo suficiente. Los otros 13 quedan diferidos: 7 paquetes/fases no necesarios, 3 condicionales y 3 sin necesidad demostrada. Todos los 22 permanecen como sub-issues nativos.

No introducir capas independientes, coordinación multi-editor o recuperación general como requisitos automáticos. La seguridad proporcional del guardado y la preservación de referencias siguen siendo requisitos; el mecanismo exacto requiere contrato revisado. P13 #2898 continúa HOLD.

Issue Prioridad vigente Impacto mínimo / motivo de diferimiento
#2892 REQUERIDO — REDUCIR Definir IDs derivados y referencias compatibles; el esquema de capas no está justificado.
#2893 DIFERIDO — NO DEMOSTRADO Separar configuración en fuentes independientes no es requisito demostrado.
#2894 REQUERIDO — REDUCIR Conservar seguridad al guardar el cambio mínimo; el protocolo físico completo no está justificado.
#2895 DIFERIDO — NO NECESARIO COMO PAQUETE Coordinación entre múltiples editores no requerida.
#2896 DIFERIDO — NO NECESARIO COMO PAQUETE Reservas de actividad no justificadas; protección local sólo si un riesgo concreto la requiere.
#2960 DIFERIDO — NO NECESARIO COMO FASE Validación de pares depende del mecanismo mínimo elegido; no es prerrequisito automático.
#2897 REQUERIDO — REDUCIR Conservar selecciones y adaptar referencias anteriores cuando cambia la identidad.
#2898 DIFERIDO — NO DEMOSTRADO Nuevo registro de proyectos no justificado; coherencia sólo si resulta afectada.
#2899 REQUERIDO — REDUCIR Resolver y lanzar la configuración correcta mediante el nuevo ID, reutilizando contratos existentes.
#2900 DIFERIDO — NO NECESARIO COMO PAQUETE Nuevos envelopes de referencias de capas no son requeridos para transportar IDs.
#2901 DIFERIDO — NO NECESARIO COMO PAQUETE Sistema general de recibos de guardado no justificado para el objetivo.
#2902 REQUERIDO — REDUCIR Conservar compatibilidad de carga con identidad y referencias; adaptar sólo incompatibilidades reales, sin coordinador nuevo.
#2903 DIFERIDO — CONDICIONAL Cambiar llamadas al cargador sólo si quedan incompatibles con el contrato mínimo.
#2904 DIFERIDO — NO NECESARIO COMO PAQUETE Convertir cargadores a asíncronos no es requerido por cambiar IDs.
#2905 DIFERIDO — CONDICIONAL Adaptar actualización del catálogo sólo si afecta identidad o referencias.
#2906 DIFERIDO — NO NECESARIO COMO PAQUETE Nuevo contrato IPC de capas no justificado; los campos actuales transportan IDs.
#2907 DIFERIDO — CONDICIONAL Conservar borrador y comunicar fallos según guardado elegido; panel general de recuperación no justificado.
#2908 REQUERIDO — REDUCIR Integrar generación y validación de IDs en productores reales; no activar el protocolo amplio.
#2909 REQUERIDO — REDUCIR Adaptar altas, edición, validación y referencias CLI con una regla compartida.
#2910 REQUERIDO — REDUCIR Settings adopta IDs definitivos y conserva vínculos; sin editor completo de capas.
#2911 DIFERIDO — SIN CAMBIO PROPIO DEMOSTRADO Selector ya transmite el ID; modificarlo sólo ante incompatibilidad demostrada.
#2912 REQUERIDO — REDUCIR Documentación mínima de regla de ID y compatibilidad junto al cambio funcional.

Evidencia y autorización

Auditoría secuencial de los 22 hijos, cinco perspectivas y síntesis por issue, con purga entre rondas. Base main d823839. Artefactos locales: room-shared/e2432-necessity-audit/. Usuario autorizó registrar esta resolución en Epic e hijos; la implementación posterior debe ceñirse al núcleo mínimo y resolver decisiones pendientes.


Especificación anterior — antecedente histórico

La tabla, gates y dependencias anteriores se preservan para trazabilidad; no son la prioridad vigente.

Part of epic #2429. Replaces the original label-only specification with the user-approved configuration identity and independent source-layer design.

Result

Reject identical calculated configurations inside each file; allow them in distinct files. Persist differentiated labels for different configurations. Settings edits a selected independent layer; the picker selects and applies it. Preserve references/defaults/locks/history and recoverable persistence.

Frozen specification

Canonical: D:/0_repos/AgentsCommander_iac/.ac/plans/2432-identity-layers/plan-v17-identity-layers.md
Plan-SHA256: 8393829484bb61d01034a79b6a5f1fb095bdf66927ee0854911b64681b884622
Scope: 53 existing paths, 21 sequential phases. Four exactbytes design agreements complete; human 7.5 pending.

Phases

|Phase|Child|Owner|Class|Files|Depends on|Phase-SHA256|

|---|---|---|---|---:|---|---|

|P01|#2892|Rust|design-bearing|3|none|6bdd7798971f4975cf958abe1159052842a93a37b04ad477a3e70b26feb5b3ae|

|P02|#2893|Rust|design-bearing|4|P01|1b6d792f2380e02aef3a3c9775378c104f73fd7735c5a9a9ab6dd57133e765de|

|P10|#2894|Rust|design-bearing|4|P02|3b978bb33b9930d447d357159120202ed29ffbcdff70237317e37504e9a46ead|

|P14|#2895|Rust|design-bearing|4|P10|9725befb47acbfc5d6dca4ce12b88e8bc082926ab4c3e348951052b1553d9e13|

|P15|#2896|Rust|design-bearing|4|P14|286fe53f75defbd1dd04db162a89f8aa11eded8e96ee1d633b1b3c075b38e102|

|P03|#2897|Rust|design-bearing|4|P15|1d9232d78f91d481c28f2a00dedcd4a06ff0e4cc6fd2bf7b5150e5353fbbcbc8|

|P13|#2898|Rust|design-bearing|9|P03|aa8a2704543482f410f72e205b37698396307aa167d4ed9919a704153b7d3036|

|P04|#2899|Rust|design-bearing|8|P13|7105e17030832d2227ca34e097d6a6c670178b5f776342dffb22f030201467cb|

|P12|#2900|Rust|design-bearing|6|P04|b6f35ca145871c416232f687c5ba7b4448628736b80d0e5451718d641d44f066|

|P16|#2901|Rust|design-bearing|4|P12|9fa8ff52e19f55b880955315ef83b469a97a3ff0942fedc67e7b187c355e744b|

|P19|#2902|Rust|design-bearing|6|P16|49d69afaa53d925c3195946060687b5276e1cec3b056976d5a996ef04fec4363|

|P20|#2903|Rust|design-bearing|8|P19|ec06c21330c1d919b3fe74412dcfe143084e1791a94b0c05906d8262abd2cd57|

|P21|#2904|Rust|design-bearing|9|P20|85f0cd35110078b83c942b5cdb67b3e98a655364e81e622200d9ca043c77e753|

|P18|#2905|Rust|design-bearing|7|P21|6784139fa7322b30bcceadd3421e9da0fea20dd97d4481485691041a440c3a30|

|P05|#2906|Rust|design-bearing|4|P18|f9bbba5e725d1e84c8b3d79708f978cb8eb0f82fc13d1de4ea5d0e5b47ed895e|

|P17|#2907|frontend|design-bearing|6|P05|f2ba0cfa6c35442a6316fe3d76093cbb28253bca01de0c2a778740034afcb00f|

|P11|#2908|Rust|design-bearing|9|P17|c5ac61b800ff9de1e2b83bb5700573760c761b2282a883e09cc5672a0b81fa26|

|P06|#2909|Rust|design-bearing|5|P11|c9b11e84178335143628f89667dfb1d62304215664206412349e24440701276b|

|P07|#2910|frontend|design-bearing|9|P06|f4bf49f92a09833ff83c8f4552357dd1e3e73defd3f02f08a0cd1849ee1a1371|

|P08|#2911|frontend|design-bearing|5|P07|d18b2b93404ab1a452a2b39e258c024c75110f9f702b7ae0c552815e2354c421|

|P09|#2912|technical-writer|design-bearing|3|P08|cc116f38227bfb9ba48c12c9776fdfb23ccab6bbacb803f0ba70be725d20f125|

Delivery boundaries

Identity mapping is prepared before human approval; real branches are created only after approval and predecessor landing. No implementation has started. Existing API behavior remains; lifecycle follow-up #2885 and #2436 remain excluded/on hold.

Activity

  1. 8 remaining items

  2. changed the title [-]Portable identity phase 3: label-uniqueness[/-] [+]Calculated coding-agent identity, independent layers and recoverable persistence[/+] on Oct 6, 2026
  3. changed the title [-]Calculated coding-agent identity, independent layers and recoverable persistence[/-] [+]IDs de agentes derivados de su ejecución — alcance mínimo[/+] on Oct 13, 2026
  4. mblua commented on Oct 18, 2026

    @mblua
    OwnerAuthor

    The user approved the proposed agents-file selectors in both Settings and the agent/profile picker, after requiring restoration of each menu's last selected file. This continues the requested change from legacy agent-ID profile links to the existing BASE id_hash, with sharing only within the selected file and no cross-file profile union. Source-local reading/writing and selected-session resolution remain to be implemented; the standalone HTML is a prototype, not delivered product behavior.

    Existing E2432 children cover the relevant concepts: #2902 actual load compatibility, #2910 Settings linkage preservation, #2899 selected launch resolution, and CLI compatibility only if affected under #2909. The user's explicit picker request now establishes minimal work for #2911, previously deferred because no separate picker change had been demonstrated. This does not activate its whole historical layer-assignment package. Exact child/phase mapping will be reconciled after formal plan consensus; no duplicate epic and no reopening delivered #3047/#3097.

    Technical score (ceremony excluded):

    Category Score Anchor and evidence
    Scope footprint 13 Multiple backend configuration/IPC and Settings/picker/helper files move together; above coherent-module anchor10, below whole-tree20.
    Diagnosis difficulty 5 Source reports already locate the ID-map and missing scoped snapshot, with remaining producer/overlay tracing; below unfamiliar-subsystem anchor10.
    Domain knowledge 9 Source ownership, normalized hash units and load/save rules form a subsystem contract near anchor10; no new cryptography.
    Solution-space ambiguity 10 Several existing enumeration/read/save seams must be reconciled; user has settled visible behavior and sharing.
    Blast radius and reversibility 11 Shared config/profile resolution with persisted migration; preflight preserves conflicts, above shared-path10 and below destructive20.
    Dependency/integration 8 Existing Rust/IPC/frontend integration, no new external service; below external-contract10.
    Verification difficulty 11 Existing harnesses need source-isolation/migration/draft/reopen fixtures and meaningful independent proof, just above new-test anchor10.
    State/data/compatibility 15 Live legacy map keys, source schemas, attachments and remembered file state; above straightforward migration10.
    Concurrency/timing 7 One editor, asynchronous source changes/saves need stale-response ownership; below multithreaded anchor10.
    Environment/tooling 3 Existing pinned Windows/CI toolchains, no new packaging/toolchain problem.

    Raw sum: 92. Final: round((92-10)/190*99)+1 = 44/100.

    Excluded: issues/branches/PRs, waiting for CI, delegation/review rounds, messaging, merge/cleanup and version/release ceremony. Full workflow is required despite score44 because source/IPC/schema/persistence and multiple owners change. Architect authors; Rust/frontend owners and both Grinches review exact applicable digests. State15 requires architect identity and verification11 requires independent proof review. No implementation or final executable build has started.

  5. mblua commented on Oct 19, 2026

    @mblua
    OwnerAuthor

    P01 (#2902) is paused before source edits: the approved plan requires legacyProfileOrphans but omits its persisted JSON schema and rules for conflicting or malformed existing quarantine. The owner supplied a concrete same-ID/different-raw-data example; the architect must define the contract and obtain the required exact-version reviews. Existing round4 approvals remain recorded, and no code/test/CI failure is claimed.

    Required remaining-work rescore: original 44 (raw92), remaining 44 (raw92); Full remains required. The same seven-phase schema/source/runtime/IPC/UI work remains, and this preservation requirement was already included.

    Category Original Remaining Anchor
    Scope 13 13 Cross-module backend and UI inventory, above coherent-module10
    Diagnosis 5 5 Exact source seams and missing contract known, below unfamiliar-subsystem10
    Domain 9 9 Source formats/hash/restore rules, near subsystem10
    Ambiguity 10 10 Architecture must select a precise compatible representation/policy
    Blast radius 11 11 Shared live-profile persistence, above shared-path10
    Integration 8 8 Existing backend/frontend/carrier contracts, near one-contract10
    Verification 11 11 Existing fixtures plus real-consumer/restore decoy controls
    State 15 15 Live schema/unknown/orphan compatibility between10and20
    Concurrency 7 7 Existing owner/lock/revision and stale-response controls
    Environment 3 3 Existing locked tools/configured CI; no environment repair

    Normalization: round((92-10)/190*99)+1=44. Excluded ceremony: issue/branch/PR operations, review rounds, delegation/messages, CI wait, merge/cleanup and version work. Complete anchored rerun and concrete blocker: room-shared/profile-hash-link-intake/remaining-score-after-orphan-contract-v1.md and p01-contract-blocker-round4-disposition-v1.md. Scope is unchanged; no new registry, history framework, harness or product question is authorized. The clean current-base PRE is retained for reuse if the source/base remain identical.

  6. mblua commented on Oct 19, 2026

    @mblua
    OwnerAuthor

    Round5: no consensus yet. Rust/UI approve; both Grinches request the same explicit duplicate-member strictness scope/read policy for registered sources. The orphan wire/collision/idempotence gap is resolved; source remains unchanged and P01 paused.

    Remaining technical score after round5 parser-scope gap

    Original44/raw92; remaining44/raw92. All7 implementation phases remain; no application source mutation/delivery. The quarantine field and lossless retention requirement were already part of the approved persisted-state scope. The orphan representation is now specified; duplicate-member rejection scope/read compatibility needs one precise reviewed decision inside the same two files, not a larger product surface.

    Category Original Remaining Anchor/evidence
    Scope footprint 13 13 Above coherent-module10: backend storage/source/runtime/IPC and two UI consumers across the same approved file inventory.
    Diagnosis difficulty 5 5 Below unfamiliar-subsystem10: current seams and the exact remaining parser-scope gap are directly identified.
    Domain knowledge 9 9 Near subsystem10: physical registered/catalog formats, existing hashing, source references and runtime restore rules.
    Solution-space ambiguity 10 10 Two/three viable representation/compatibility approaches; strictness scope/read policy must be chosen by architecture.
    Blast radius/reversibility 11 11 Above shared-path10: live profiles may be lost if conversion is wrong; existing preflight/atomic publication limits damage.
    Dependency/integration load 8 8 Near one-contract10: defined backend/frontend/carrier handoffs within this repo, no new external service.
    Verification difficulty 11 11 Above harness-supported10: real callback and restore provenance need decoys/positive controls in existing fixtures.
    State/data/compatibility 15 15 Between persisted-state10 and live-wire20: versioned physical schema, unknown/orphan preservation and old ID compatibility.
    Concurrency/timing 7 7 Below async clear-owner10: existing owner/catalog locks and revision guards, stale UI replies, no new lock framework.
    Environment/tooling 3 3 Near standard-environment1: locked existing Windows toolchain and configured remote CI; environment is not the problem.

    Raw92; round((92-10)/190*99)+1 =44. Full retained (multiple owners/contracts/source architecture, State15, Verification11). No score reduction for a prose-only correction when the actual remaining implementation is unchanged. Excluded ceremony: issue edits, branch/PR mechanics, planning/review rounds, delegation/messages, CI wait, merging/cleanup, changelog/version work. Actual required fixtures remain part of verification cost, not ceremony.

  7. mblua commented on Oct 20, 2026

    @mblua
    OwnerAuthor

    P02 / #2905 cross-platform verification: PENDING_LINUX_TESTS. Developed on Windows.

    PR #3141 targets main at feature head 309b6e9; NOT YET ON origin/main, required exact-head CI pending. Available Windows checks, both reviews and full structural POST passed.

    Missing: native Unix physical owner-directory replacement test and exact-SHA nonzero runtime result documented in #2905. Windows F1 is simulated verifier failure, not physical Unix proof.

    Explicit user 2026-09-09 cross-OS policy defers only this unavailable runtime test across protected landing; no failure/required CI waiver or frozen-plan byte change. Mirror developed-windows and requires-test-linux here while child evidence is pending. Keep Epic and #2905 open; P03 remains gated. Exact landed main SHA and user-routed Linux instructions will follow in #2905 after merge.

  8. mblua commented on Oct 21, 2026

    @mblua
    OwnerAuthor

    P02 protected landing milestone: PR #3141 is MERGED into origin/main at e78d199 (tested feature 3dc8d6f, identical merge tree). Exact-head required/applicable CI, available Windows checks and both independent reviews passed; the two overlay fixture failures are resolved.

    PENDING_LINUX_TESTS remains. #2905 stays OPEN with the native physical owner-directory substitution test, exact command, expected 1 selected / 1 PASS / 0 ignored, setup and return-evidence requirements here: #2905 (comment)

    Keep epic #2432 OPEN and retain developed-windows + requires-test-linux. P03 and later dependent phases stay gated until the real Unix result is verified/reconciled. Windows simulation, Linux Clippy compilation and configured tier skips are not Unix runtime proof. Under the explicit 2026-09-09 policy, the user routes the Linux group to this shared issue; no all-platform or whole-feature completion is claimed.

  9. removed
    requires-test-linuxLinux testing is pending; report results in this issue.
    on Oct 21, 2026
  10. mblua commented on Oct 21, 2026

    @mblua
    OwnerAuthor

    P02/#2905 is delivered and closed: #2905 (comment). PR #3141 is merged at e78d199. The user explicitly accepted closure without the pending physical Unix test (UNEXECUTED / NOT_PASS); this supersedes the prior Linux handoff for P02 only. P01 and P02 are complete. P03-P07 remain sequential and this epic stays OPEN. P03 persists source references in existing selection/default/session carriers; P04 activates them for launch/restart/restore.

  11. mblua commented on Oct 21, 2026

    @mblua
    OwnerAuthor

    Selected-file P03 delivered; #2900 CLOSED via PR #3144. Main f705437; tested source 27f1afd, identical merge tree. P01/#2902, P02/#2905 and P03/#2900 delivered. P04/#2899, P05/#2906, P06/#2910 and P07/#2911 remain sequentially pending; Epic stays OPEN.

    P03 preserves references in existing carriers; actual runtime source resolution remains P04.113 distinct local tests and both source/proof reviews passed. Required exact-head CI passed, configured full=false omissions justified; no failure waived. Full pair/SCC/arc identity retained, known cycles remain. No final executable requested.

    Immutable overallv14/P03v4, phase-issues.json and approved-identities-v7 exact original-five consensus unchanged. Evidence room-shared/e2432-selected-file-profiles/execution/P03/p03-final-ci-and-landing-authority-v1.json and p03-delivery-cleanup-receipt-v1.json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    EpicLarge cross-cutting work itemdeveloped-windowsDeveloped on Windows.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions