General Proposal · Proposed / Non-Authoritative

Architecture Level · HTML-only HDO dogfood variance

Consultant-operative architecture

A decision board for commissioning one traceable, testable Consultant operative across standard, skill, shared instructions, runtime adoption, interfaces, legacy transition, and delegation controls.

Checkpoint: T101-PH000-AC001-CHECK000
Review cycle: 1
Date: 2026-07-11
Revision: v0.1.0
Status: Pending HDO disposition
Decision owner: HDO
Current state: 0 / 15 dispositioned

Authority boundary. CHECK000 permits authoring and assurance of this commissioning package only until HDO disposition, merge, and a merge-hash-bound #477 ledger record complete the proof path. It grants no execution; child issue minting; board mutation; delegation reinstatement; legacy retirement; shared, root, external-runtime, or cross-initiative implementation; parent closure; or client release.

#325 HDO dogfood variance. This single-file HTML is both the semantic proposal source and the HDO review surface. By explicit HDO direction there is no JSON or Markdown companion. The variance is labeled, not concealed, and creates no authority beyond CHECK000 authoring and assurance.

All calls pendingRecommendations are Consultant synthesis for independent HDO disposition. No radio option is preselected; one lane never implies the state of the other.

Architecture decisions · AD0 / 8 dispositioned

Governance decisions · GD0 / 7 dispositioned

Orientation

What is being decided

The Architecture lane decides the durable Consultant-operative contract and where its semantics, procedure, entrypoints, runtime projection, interfaces, guardrails, and legacy transition belong. The Governance lane decides decomposition, authority, evidence, suspension, assurance, retirement, and commissioning proof. All fifteen calls are pending and independent.

Semantic authority

One Consultant contract

Standard clauses define identity, limits, interfaces, and delegation doctrine.

Operative mechanics

Procedure and projection

Skill, root entrypoints, package, runtime adoption, tests, and preserved rollback remain distinct.

Grounded constraints

What the evidence establishes

Merged and observed evidence

PR #476 authorizes CHECK000 package preparation, not activity execution.
PR #470 records split-brain identity, inherited-model failure, absent session boot, and prompt/runtime drift.
SES003 requires HDO-triggered Fable, explicit model, and announcement/disposition before spawn.
All formerly pre-approved delegation categories remain suspended.

Binding limits

T103 and P-level doctrine own portability, projection, and shared instruction mechanics.
The active global Consultant skill collides with the intended operative and cannot be overwritten here.
Legacy profiles are materially distinct and cannot be treated as disposable duplicates.
Issue #354 supplies only the Consultant-side Reviewer interface; non-Consultant identities remain outside T101.

Prompt-specific judgment

What remains Consultant synthesis

Recommended architecture

One combined T101-STD-001; standard semantics, skill procedure, concise shared entrypoints, separately governed distribution and runtime adoption, preserved legacy inputs, and interface invariants bounded to the Consultant side.

Recommended control path

Four sequential vertical slices, fresh full-package CHECK001 assurance, then HDO GATE001 dispositions for standard acceptance, adoption, retirement, and each delegation category. Implementation can establish eligibility, never reinstatement.

Architecture comparison

Layered operative versus collapsed alternatives

Criterion	Layered combined standard	Three standards	Prompt/skill as authority
Single precedence chain	Strong	Cross-file risk	Runtime drift
Progressive disclosure	Strong	Mixed	Strong
Runtime rollback	Explicit	Explicit	Implicit
Legacy coverage	Mapped and reversible	Fragmented	Unclear

Recommendation: layer the surfaces instead of treating generated or served procedure as normative. This is a commissioning judgment grounded by observed drift; it is not accepted until the HDO dispositions AD-01 through AD-08.

5–6

Independent decision lanes

Architecture and governance dispositions

Each card states a recommendation, reasoning, a genuine alternative with consequence delta, downstream impact, and an evidence boundary. Every control begins pending.

Filter

Architecture lane · AD

What the Consultant-operative architecture should encode · 8 decisions

AD-01Combined standard shapePending

Should one standard own the tightly coupled Consultant operative?

Recommendation

Commission one combined T101-STD-001 with substandards for identity/authority, autonomy/evaluation, delegation/interfaces, and runtime adoption; preserve T101-STD-002/003 as deprecated registry lineage only after acceptance.

Reasoning

One operative needs one precedence and amendment chain.

Alternative + consequence delta

Three independent standards preserve reserved labels but create cross-file precedence and coordinated-amendment risk.

Downstream impact

TK001 structure, SPS index, successor references, and GATE001 acceptance.

GAP-001 · Consultant recommendation

Non-binding illustrative Detail · substandard map

T101-STD-001 → identity/authority | autonomy/evaluation | delegation/interfaces | adoption

Evidence boundary

The draft reservations show fragmentation; no accepted source has yet selected the combined shape.

AD-02Authority layeringPending

Which surface owns semantics, procedure, entry, distribution, adoption, and execution?

Recommendation

Standard = semantics; skill = procedure; root instructions = concise shared entry; portable package = distribution source; machine/global runtime = projection; issues/plans = execution contracts.

Reasoning

Distinct owners prevent served or generated state from becoming silently normative.

Alternative + consequence delta

Treat the skill or root prompt as full authority; this is simpler but creates semantic drift and ambiguous precedence.

Downstream impact

Clause boundaries, skill references, T103 coordination, and validation.

GAP-003/004 · T103 boundary

Evidence boundary

T103 establishes distinct mechanics owners; the exact T101 allocation remains an HDO architecture decision.

AD-03Root audience splitPending

What belongs in AGENTS.md, CLAUDE.md, and the Consultant skill?

Recommendation

Mirror universal safety/execution rules, keep tool mechanics bounded, and move Consultant persona/protocol plus AskUserQuestion prohibition into the skill. Any root edit needs exact P-level authority.

Reasoning

Root files are shared entrypoints, not persona bundles.

Alternative + consequence delta

Make CLAUDE.md the Consultant directive and AGENTS.md the executor directive; visible, but inconsistent across runtimes and outside their shared purpose.

Downstream impact

TK002 diff scope, P-level mandate, cross-harness consistency.

GAP-003 · provisional T103 mechanics

Evidence boundary

Current roots carry routing content; CHECK000 cannot itself authorize their modification.

AD-04Skill source and runtime adoptionPending

How should the repository source reach the active global collision?

Recommendation

Author a repo-governed skills/consultant; use T103 packaging/projection; adopt to an exact external target only through a separately recorded target/hash/rollback act.

Reasoning

Reviewed source authorship does not prove or authorize active runtime projection.

Alternative + consequence delta

Directly replace the global skill; faster, but bypasses source review, collision handling, rollback, and deployment authority.

Downstream impact

TK002 source, TK003 adoption, parity evidence, rollback.

Runtime readlink evidence · GAP-004

Evidence boundary

The collision is observed; no runtime or deployment write is authorized at CHECK000.

AD-05Corrected R-05 precedencePending

Can an in-session HDO instruction silently outrank accepted clause text?

Recommendation

Accepted higher-altitude sources govern. HDO may authorize an explicit, scoped, durable variance or amendment; material conflict stops affected execution until recorded disposition. Suspected stale doctrine is routed, not opportunistically archived.

Reasoning

This preserves HDO authority without destroying auditable precedence.

Alternative + consequence delta

Original R-05 gives in-session HDO statements automatic precedence; responsive, but permits unrecorded override.

Downstream impact

TK001 clauses, TK002 session behavior, variance records, fail-closed conflict handling.

GAP-002 · P-STD-008-CLAUSE-002D

Evidence boundary

The conflict is established; the corrected wording is proposed doctrine pending HDO disposition.

AD-06Delegation guardrail enforcementPending

What must a Consultant spawn protocol enforce?

Recommendation

Require pre-spawn announcement, explicit model/effort/scope/permissions/output, HDO disposition, explicit model field, Fable deny-by-default unless HDO-triggered, positive/negative tests, and fail-closed regression recording.

Reasoning

Prose reminders already failed under inherited-model behavior.

Alternative + consequence delta

Repeat reminders in root files and memories; low cost, but no enforcement or negative proof.

Downstream impact

TK002 protocol/validator and TK004 regression evidence.

SES003 DEC001/DEC002 · PR #470

Evidence boundary

The guardrails are durable HDO decisions; implementation and test design remain future authorized work.

AD-07Counterparty interface boundaryPending

How much of other roles belongs inside T101?

Recommendation

Standard clauses define invariant Consultant-side contracts; skill references hold packets/runbooks; the Reviewer interface includes all six #354 requirements. Route non-Consultant identities to #475.

Reasoning

The Consultant needs testable interfaces without pre-empting P-level role architecture.

Alternative + consequence delta

Define full counterpart identities in T101; reduces indirection but exceeds the Consultant-only charter.

Downstream impact

TK004 contracts, #354 coverage, #475 routing.

GAP-006 · issue #354 boundary

Evidence boundary

Six interface inputs are accepted; counterpart role identity is explicitly outside this activity.

AD-08Legacy transitionPending

When may legacy Consultant files redirect or retire?

Recommendation

Map each file to adopted/rejected/preserved content; keep originals live or frozen through replacement tests and adoption; then redirect/archive only with reversible rollback. Never delete distinct lineage.

Reasoning

The legacy inventory contains materially distinct fallback inputs.

Alternative + consequence delta

Bulk archive at implementation start; shortens overlap but risks coverage loss and removes rollback before proof.

Downstream impact

TK003 mapping/adoption and GD-06 GATE001 retirement calls.

GAP-007 · legacy inventory

Evidence boundary

Distinct content is observed; no legacy edit or retirement is authorized by CHECK000.

Governance lane · GD

How commissioning becomes executable and provable · 7 decisions

GD-01Frozen decompositionPending

What sequence should an approving CHECK000 freeze?

Recommendation

Four sequential tasks: standard/authority; skill/root boundary; runtime/legacy; interfaces/evaluation/delegation; then independent CHECK001 and HITL GATE001.

Reasoning

Vertical slices preserve end-to-end acceptance and ordered dependencies.

Alternative + consequence delta

Seven to ten file-family tasks improve local ownership but fragment acceptance and multiply shared-surface coordination.

Downstream impact

Plan register, post-proof issue templates, sequencing.

GAP-009 · plan register

Evidence boundary

The parent names outcomes; only approving disposition plus merge plus ledger freezes/mints the rows.

GD-02Cross-surface authorityPending

What later write authority may CHECK000 grant?

Recommendation

Grant only exact named surfaces; root P-level and external targets require explicit clauses, parallel-work check, diff/hash proof, rollback, and no credential/state movement.

Reasoning

Outcome intent does not imply source-owner or deployment authority.

Alternative + consequence delta

Infer writes from AC001 outcomes; faster, but obscures cross-repo effects and violates ownership boundaries.

Downstream impact

TK002/TK003 contracts and evidence.

Authority audit · T103/P owners

Evidence boundary

This proposal requests future bounded mandates; it performs and authorizes none of the writes.

GD-03Reinstatement evidencePending

What evidence makes one delegation category dispositionable?

Recommendation

Require policy encoding, enforcement, success and negative tests, trace, permission check, regression trigger, rollback/suspension, independent review, and a separate HDO call per category.

Reasoning

Category-level proof prevents one passing surface masking another category’s gap.

Alternative + consequence delta

Reinstate the historic table when the skill exists; simple, but all-or-nothing and unproven.

Downstream impact

TK004 matrix, CHECK001, GATE001 calls.

GAP-008 · suspended lineage

Evidence boundary

Every category starts suspended; implementation can establish eligibility only.

GD-04Regression and revocationPending

What happens when a guardrail breaches or evidence invalidates?

Recommendation

Operationally suspend the affected category pending HDO review; only HDO reinstates, conditions, or revokes. Authority posture is not P-STD-002 work status.

Reasoning

This fails closed while reserving the durable authority act to its owner.

Alternative + consequence delta

Auto-revoke or merely log; the first over-delegates HDO authority, the second fails open.

Downstream impact

Runtime control, incident trace, GATE001 vocabulary.

GAP-008 · authority-state model

Evidence boundary

The state model is proposed; CHECK000 itself cannot reinstate or revoke any category.

GD-05Independent assurancePending

What assurance is required before GATE001?

Recommendation

Each task produces primary evidence; CHECK001 uses a fresh full-package adversarial Reviewer at exact head with behavioral, negative, runtime, and legacy tests; material changes trigger fresh full review.

Reasoning

Independent exact-head review closes the observed prose-only enforcement gap.

Alternative + consequence delta

Self-verification plus terminal HDO inspection costs less but weakens independence and regression coverage.

Downstream impact

Task acceptance, CHECK001 packet, GATE001 entry.

Plan CHECK001 profile

Evidence boundary

CHECK000 assurance reviews commissioning only; it is not future implementation evidence.

GD-06Retirement timingPending

Who decides legacy retirement and when?

Recommendation

GATE001 dispositions retirement only after content coverage, adoption, rollback, link, and archive checks; unresolved files remain preserved.

Reasoning

Replacement authorship does not prove runtime adoption or fallback safety.

Alternative + consequence delta

Let TK003 retire once replacement is authored; reduces overlap but may remove the active fallback before validation.

Downstream impact

TK003 evidence, GATE001 itemization, preservation register.

AD-08 · GAP-007

Evidence boundary

No legacy retirement occurs through CHECK000, implementation completion, or CHECK001 alone.

GD-07CHECK000 proof and mint timingPending

What completes commissioning authority?

Recommendation

The draft PR body is the checkpoint record; HDO records approve, approve_with_conditions, revise, or defer. Only approving disposition plus merge plus merge-hash-bound #477 ledger comment permits exact frozen child issues to mint.

Reasoning

Merge alone cannot safely carry conditions or complete parent-ledger proof.

Alternative + consequence delta

Treat PR merge as approval; operationally simple, but incomplete under P-STD-008-CLAUSE-005A.

Downstream impact

PR body, merge sequence, #477 ledger, child creation order.

Plan CHECK000 evidence target

Evidence boundary

Until all three proof legs exist, authoring/assurance is the only permitted CHECK000 work.

Never hidden

Open residue and gated future work

Authority

Root/shared edits, external runtime adoption, T103/P-level changes, and cross-initiative work need exact future authority; none is inferred here.

Delegation

All categories remain suspended. TK004 can make categories evidence-eligible; only HDO at GATE001 can reinstate, condition, or revoke.

Legacy

Distinct inputs stay preserved until coverage, adoption, rollback, link, archive, and HDO retirement proof all exist.

Acceptance

CHECK000 commissions work; CHECK001 assesses conformance; GATE001 independently decides standard acceptance, runtime adoption, legacy retirement, parent closure, and category posture.

Release

No CHECK000 action authorizes client release, board mutation, credentials/state movement, or deployment.

Traceability

Semantic sources and governed handoff

Copying these paths or the review record has no authority effect.

artifacts/tasks/T101/workspace/PH000/AC001/plan_T101-PH000-AC001.md

artifacts/tasks/T101/workspace/PH000/AC001/analysis/analysis_T101-PH000-AC001-CHECK000_consultant-operative-architecture.md

artifacts/tasks/T101/workspace/PH000/analysis/analysis_T101-PH000_consultant-agent-model-evidence.md

artifacts/tasks/T101/workspace/PH000/snotes/snotes_T101-PH000-SES003.md

artifacts/tasks/P/standard/standard_P-STD-008_workspace-development-lifecycle-standard.md

HDO controls and exportable decision record

All 15 T101 decisions load pending. Architecture and governance lanes remain independent. “Change” requires an alternative. The export is transient text for governed scribing; it creates no JSON or Markdown companion and is not itself authoritative.

Architecture lane

0 Accept · 0 Change · 0 Other · 8 pending

Governance lane

0 Accept · 0 Change · 0 Other · 7 pending

Exportable T101 review record