ARCHITECTURE.md section 4 now requires this, but it does not exist yet. Today the old six services offer far more than the new binary does, and the slices remove old paths on the understanding that a replacement exists, which is a weaker claim than parity.
Build one ledger listing every surface and capability of today's Archie, with one row each: workflows and the canvas, run and task views, captures, alerts, chat, the composer, services/health, audit, logs, summary, setup, config, identities/access/tokens, skills, curators, MCP servers (as tools and as an exposed server), repositories, bindings, mappings, playbooks, issue routing, schedules, secret engines, extensions, backups and restore, and the engine's guarantees.
Each row's verdict is one of: moved (with what makes it equal or better), merged (into which surface), or deleted (with the reason). A row reading "not yet there" keeps its old path alive. The old services stop only when every row is green.
Done when: the ledger exists as a table in this issue (or a page it links), the maintainer has reviewed every deletion, and no old path has been removed while its row said not yet there.
ARCHITECTURE.md section 4 now requires this, but it does not exist yet. Today the old six services offer far more than the new binary does, and the slices remove old paths on the understanding that a replacement exists, which is a weaker claim than parity.
Build one ledger listing every surface and capability of today's Archie, with one row each: workflows and the canvas, run and task views, captures, alerts, chat, the composer, services/health, audit, logs, summary, setup, config, identities/access/tokens, skills, curators, MCP servers (as tools and as an exposed server), repositories, bindings, mappings, playbooks, issue routing, schedules, secret engines, extensions, backups and restore, and the engine's guarantees.
Each row's verdict is one of: moved (with what makes it equal or better), merged (into which surface), or deleted (with the reason). A row reading "not yet there" keeps its old path alive. The old services stop only when every row is green.
Done when: the ledger exists as a table in this issue (or a page it links), the maintainer has reviewed every deletion, and no old path has been removed while its row said not yet there.
sam
added the taskhigh labels 2026-11-16 02:22:02 +00:00
Built as visual/archie-parity-ledger.html in archie-product: 48 rows over six groups, each with what it does today, a verdict (Move, Merge, Delete, Undecided), the destination, a status, a note for the planner and an approval box. Decisions and notes save in the browser; Export writes JSON, Import reads it back, Copy summary puts a compact block on the clipboard. Sealing is refused while any row is undecided and records who sealed it. Verified in a browser: persistence across reload, the refused seal with 47 undecided, and the exported snapshot. Nothing in the page is authoritative until it is sealed and exported; then this issue's done-when is this file plus the exported ledger.
Built as visual/archie-parity-ledger.html in archie-product: 48 rows over six groups, each with what it does today, a verdict (Move, Merge, Delete, Undecided), the destination, a status, a note for the planner and an approval box. Decisions and notes save in the browser; Export writes JSON, Import reads it back, Copy summary puts a compact block on the clipboard. Sealing is refused while any row is undecided and records who sealed it. Verified in a browser: persistence across reload, the refused seal with 47 undecided, and the exported snapshot. Nothing in the page is authoritative until it is sealed and exported; then this issue's done-when is this file plus the exported ledger.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ARCHITECTURE.md section 4 now requires this, but it does not exist yet. Today the old six services offer far more than the new binary does, and the slices remove old paths on the understanding that a replacement exists, which is a weaker claim than parity.
Build one ledger listing every surface and capability of today's Archie, with one row each: workflows and the canvas, run and task views, captures, alerts, chat, the composer, services/health, audit, logs, summary, setup, config, identities/access/tokens, skills, curators, MCP servers (as tools and as an exposed server), repositories, bindings, mappings, playbooks, issue routing, schedules, secret engines, extensions, backups and restore, and the engine's guarantees.
Each row's verdict is one of: moved (with what makes it equal or better), merged (into which surface), or deleted (with the reason). A row reading "not yet there" keeps its old path alive. The old services stop only when every row is green.
Done when: the ledger exists as a table in this issue (or a page it links), the maintainer has reviewed every deletion, and no old path has been removed while its row said not yet there.
Built as visual/archie-parity-ledger.html in archie-product: 48 rows over six groups, each with what it does today, a verdict (Move, Merge, Delete, Undecided), the destination, a status, a note for the planner and an approval box. Decisions and notes save in the browser; Export writes JSON, Import reads it back, Copy summary puts a compact block on the clipboard. Sealing is refused while any row is undecided and records who sealed it. Verified in a browser: persistence across reload, the refused seal with 47 undecided, and the exported snapshot. Nothing in the page is authoritative until it is sealed and exported; then this issue's done-when is this file plus the exported ledger.