converge(ENCODE): operator-surface.v1 DRAFT contract + repo vision extended to two seams (owner-ratified 2026-09-04) - #79
Merged
Conversation
…tended to two seams (owner-ratified 2026-09-04)
… SYNC re-hash with full ledger re-review Owner reviewed the DRAFT text at the operator-surface ENCODE gate and ratified it (literal: "lgtm."). Both documents record that in their Changelog; both stay **Status: DRAFT** -- ratification of the text is not a freeze. `docs/VISION.md` moving broke `CCV1-000`'s pin, which mandates a full ledger re-review, never a silent hash bump (LEDGER-FORMAT.md sec.4): docs/VISION.md b7547519... -> f5eb400c... contracts/custody-coordination.v1.md ec4b736f... (unchanged, re-verified) 24 rows walked; 0 re-anchored -- every contract-quoting row anchors into the custody contract, whose bytes did not move, and no row quotes vision text, so the two vision lines that did change (Scope, Governing contract) are cited by no row. Dispositions re-checked against the tree, not assumed: unchanged at 22 CONFORMS / 2 NOT-ASSERTABLE / 0 VIOLATION / 0 GAP (`pytest ledger/checks -q` 26 passed; `make ledger-mutate` 15/15 mutations still flip their probe red). Recorded in `ledger/reconcile-report.md` as a dated re-review section, an updated SYNC block, and a Changelog entry. `contracts/operator-surface.v1.md` is deliberately not pinned in CCV1-000 and carries no rows yet: it is seeded as its own OSV1-### family in a following step.
Brian Krabach (bkrabach)
deleted the
converge/encode-operator-surface
branch
September 4, 2026 15:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Converge Phase 2 ENCODE for the human-facing operator surface (L0 Mission Control / L1 Project Observatory / L2 Item Detail, login/setup/trust, PWA).
Ratification record. Decisions ratified 2026-09-04 with the owner's literal words: "Let's make hero the velocity, along w/ other numbers that matter, such as the active/in-flight, blocked, need attention, open, etc. Focus is on observability, etc. The rest looks good to me." DRAFT text ratified: "lgtm." Status on both documents remains DRAFT.
Evidence chain (under
.amplifier/converge/in the workspace, not this repo): Phase-0 briefs A (shipped surface, 30 routes, 137 inline styles, zero visual assertions) + B (prior decisions, council verdict, 15 verbatim invariants) → Phase-1 negotiator minutes (9 decisions) → protocol-authority rulings (human-perception seam admissible; typed-exemption is Core but the register/ceiling live in the ledger; one-way bare-id citation of custody Core 8/14, custody file untouched; CLI--jsonReserved; ONE VISION.md per repo; human look = ratification input only).contracts/operator-surface.v1.md(new, DRAFT)13 Core clauses each with a Machine check and Tier (A = in-process static/HTML/token; B = real-browser emitting orchestrator-re-checked artifacts; 2 NOT-ASSERTABLE named as such): hero = fleet velocity + in-flight/blocked/needs-attention/open · closed status-hue set, calm paints zero alarm pixels · state never colour-only · one source of visual truth (literal colour/font/size inline = violation) · reads never write · views survive their body-swap incl. announcements · perception floors measured (≥4.5:1/≥3:1/≥44px/reduced-motion) · calm reported never celebrated, empty states keep slot · no JS framework/build step/plugin loader · anti-goals (no kanban, no refresh-dying state, no new chart lib, no unbounded queries) · push on custody-TTL breach only · forms never lead (N-A) · alarm-to-acknowledgement is the outcome (N-A). 8 Backlogged with named triggers · 7 Conformance good/bad pairs · 6 Reserved · Freeze 1–10 (conditions, never status). Changelog records the rejected hero-as-age alternative and its rationale.
docs/VISION.md(extended — the one repo vision, two seams)Scope + governing-contract pointer edited; new "The Operator Surface" section with the owner-ratified purpose sentence and Principles 8–12; four anti-goals appended. Custody text byte-identical.
Mandatory ledger re-review (SYNC hash changed)
CCV1-000VISION hashb754…da4c→f5eb…5013; custody contract hash unchanged (re-verified). 0 rows needed re-anchoring (no row cites the two changed vision lines). Dispositions re-checked on this tree: 22 CONFORMS / 2 NOT-ASSERTABLE.pytest ledger/checks26 passed ·make ledger-mutate15/15 · ruff clean.reconcile-report.mdcarries the dated re-review. TheOSV1-###row family is seeded in the next step, not here.🤖 Generated with Amplifier