Skip to content

Reconcile P-NEUTRAL completion in Architect Session #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pcvantol merged 1 commit into from
Sep 6, 2026
Merged

Reconcile P-NEUTRAL completion in Architect Session #44

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
66 changes: 52 additions & 14 deletions ARCHITECT_SESSION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,8 @@ Before reaching an architecture conclusion:
4. Inspect every open EP architecture, roadmap, migration and P-NEUTRAL PR,
recording its exact head. Inspect current Forge consumer requirements/open
proposals, Forge Platform installation/deployment authority, and relevant
Workspace dependency documents at their `main` revisions.
Workspace dependency documents at their freshly resolved remote `origin/main`
revisions. Do not use a local peer checkout as current peer authority.
5. Inspect the actual installed EP instance separately: service/health,
installation identity/data root, CENTRAL schema/integrity, installed wheel
and CLI, ingress availability, credential/auth boundary, attached project,
Expand All @@ -73,6 +74,23 @@ authority maps; `EXECUTION_HOST_ARCHITECTURE.md`; `RUN_QUALIFICATION_EVIDENCE_CO
and the phase-P migration/dependency authorities above. Follow their links for
the narrow contract at issue rather than inventing a parallel summary.

## Peer authority freshness

Before using time-sensitive Forge or Workspace status, refresh that
repository's remote state and resolve its `origin/main`. Record the repository,
exact SHA and observation timestamp. A previously observed SHA is historical
observation evidence only; local filesystem timestamps do not establish
freshness. If either refresh or remote resolution is unavailable, record:

```text
PEER_AUTHORITY_FRESHNESS = UNVERIFIED
```

and do not present time-sensitive peer status as current. Otherwise record
`PEER_AUTHORITY_FRESHNESS = VERIFIED`. EP owns EP capability status; consumer
repositories own only their dependency semantics. Do not turn a peer's
projection into a second EP roadmap.

## Evidence labels

Every material statement must carry one of these labels:
Expand All @@ -89,9 +107,17 @@ Every material statement must carry one of these labels:
| `INFERENCE` | A conclusion derived from evidence; never silently promoted. |
| `PROPOSAL` | A suggested future change awaiting its owner. |

Always distinguish `IMPLEMENTED`, `QUALIFIED`, `AVAILABLE_TO_CONSUMER`, and
`DOCUMENTED_STATUS`. No one implies another. If they disagree, record a stale
projection or an unresolved conflict instead of flattening the states.
Every material current-status conclusion records `DOCUMENTED_STATUS`,
`IMPLEMENTED`, `QUALIFIED`, `COMPLETION_EVIDENCE`,
`AVAILABLE_TO_CONSUMER`, and `CURRENT_RECONCILED_STATUS`. No one implies
another. If a roadmap/DAG/status projection says `ACTIVE`, `PLANNED`, or
`INCOMPLETE` while stronger same-capability owning-repository canonical
completion or qualification evidence proves closure, set
`STALE_PROJECTION_SUSPECTED = TRUE`, inspect the scope of the evidence, and
repair the owning current-status projection. Roadmap order is not stronger
than canonical completion evidence. Implementation alone never implies
qualification. `CURRENT_STATUS_IS_EVIDENCE_RECONCILED = TRUE` is required
before reporting a status as current.

## Two-pass bootstrap

Expand All @@ -104,13 +130,19 @@ state; open EP proposals; and peer consumer requirements. Label the result

### Pass 2 — Evidence Reconciliation

Test whether roadmap projections are stale, a historical umbrella gate is
being treated as atomic, implementation has advanced without qualification,
Compare within EP as well as across products: roadmap, dependency DAG, status
projections, completion/qualification evidence, implementation evidence and
merged canonical history. Classify each finding as `NO_CONFLICT`,
`STALE_PROJECTION_SUSPECTED`, `PENDING_RECONCILIATION`, or
`REAL_AUTHORITY_CONFLICT`. Test whether roadmap projections are stale, a
historical umbrella gate is being treated as atomic, implementation has advanced without qualification,
qualification is unavailable to the consumer, historic migration ordering is
being confused with a physical dependency, a peer needs only a bounded
producer capability, an open PR contains a supported successor, or an
installed runtime already supplies a producer seam. Do not rewrite Pass 1;
write only supported, owned findings back to their canonical record.
write only supported, owned findings back to their canonical record. A stale
current-status projection is normally an autonomous documentation/status
repair, not automatically a human architecture decision.

## First-loop objective and dependency test

Expand Down Expand Up @@ -241,6 +273,7 @@ roadmap/DAG proposal; do not create competing P-NEUTRAL or roadmap truths.
| Governance change | governance documents |
| Execution contract change | owning execution contract |
| Migration authority finding | owning migration/authority document |
| Stale current status | owning roadmap/status/DAG projection |
| Bootstrap method change | this file |
| Peer-product truth | peer authority; reference it, do not duplicate it as EP authority |
| Transient reasoning | do not persist |
Expand All @@ -257,11 +290,12 @@ without chat history.

Every substantive Architect response ends with a compact ASCII progress report.
It is a read-time evidence projection, not a fourth roadmap or an independent
status register. Derive the shared rows afresh from the current owning
repository `main` authorities, their exact SHA/date where material, canonical
producer evidence, and open-PR head/qualification state. Name those sources in
`SOURCES`; never copy a peer's status into this file or silently promote a
`PENDING_PR` to canonical truth.
status register. Derive the shared rows afresh from current remote
`origin/main` owning authorities, their exact SHA and observation timestamp,
canonical producer evidence, and open-PR head/qualification state. Never copy
a peer's status into this file or silently promote a `PENDING_PR` to canonical
truth. If peer freshness is unverified, say so and omit time-sensitive peer
status claims.

Use capability/evidence rows only — a status is never inferred from ordering,
elapsed time, or an approximate percentage. Every row must use exactly one of:
Expand All @@ -275,8 +309,12 @@ The report must include both shared sections and this product-specific section:

```text
ARCHITECT PROGRESS
SOURCES: Forge main=<SHA/date>; EP main=<SHA/date>; Workspace main=<SHA/date>;
pending=<PR/head/check state or none>
SOURCES
Forge origin/main=<SHA>@<observed-at>
EP origin/main=<SHA>@<observed-at>
Workspace origin/main=<SHA>@<observed-at>
PEER_AUTHORITY_FRESHNESS=VERIFIED | UNVERIFIED
pending=<PR/head/check state or none>

AUTONOMY CUTOVER
<status> <capability> — <producer/qualification evidence and classification>
Expand Down
6 changes: 3 additions & 3 deletions docs/development/ENGINEERING_PLATFORM_EXTRACTION_MIGRATION_PLAN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -807,10 +807,10 @@ It is not a shorthand that permits an unspecified migration prerequisite.
| Node ID | Depends on | Provides / qualification | Current status | V1 classification |
| --- | --- | --- | --- | --- |
| `EP::PHASE3_STANDALONE_PACKAGE_AND_INSTALL_QUALIFICATION_V1` | Phase-0/1 completed boundary and the clean-slate Phase-2 decision | History-preserving extraction; clean package/import; schema-41 clean store; Server and minimum Agent installation/service qualification; B8C/B8D evidence | AUTHORIZED / incomplete | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_TRANSPORT_V1` | Retained P-CENTRAL-CORE and P-CENTRAL-CONSOLE repairs | File, CLI and HTTP normalize into CENTRAL; watcher owns no lifecycle truth | ACTIVE GAP | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_TRANSPORT_V1` | Retained P-CENTRAL-CORE and P-CENTRAL-CONSOLE repairs | File, CLI and HTTP normalize into CENTRAL; watcher owns no lifecycle truth | COMPLETE / qualified P-TRANSPORT ingress evidence | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_QUEUE_V1` | `EP::P_TRANSPORT_V1` | Project-scoped FIFO, lease/recovery/finalization and isolation evidence | QUALIFICATION REMAINS | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_NEUTRAL_V1` | `EP::P_QUEUE_V1` | No active DJConnect runtime identity, local authority or obsolete entrypoint | ACTIVE GAP | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_INSTALLER_V1` | `EP::PHASE3_STANDALONE_PACKAGE_AND_INSTALL_QUALIFICATION_V1`; `EP::P_NEUTRAL_V1` | Idempotent verified installation, service, repair and clean activation path | PLANNED / incomplete | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_NEUTRAL_V1` | `EP::P_QUEUE_V1` | No active DJConnect runtime identity, local authority or obsolete entrypoint | COMPLETE / merged closure `b44af0914622dd57c5c5c2266ee2caf9b31d9007` | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_INSTALLER_V1` | `EP::PHASE3_STANDALONE_PACKAGE_AND_INSTALL_QUALIFICATION_V1`; `EP::P_NEUTRAL_V1` | Idempotent verified installation, service, repair and clean activation path | CURRENT AUTONOMY FRONTIER / incomplete | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::P_RELEASE_V1` | `EP::PHASE3_STANDALONE_PACKAGE_AND_INSTALL_QUALIFICATION_V1`; `EP::P_INSTALLER_V1` | Pinned signed release, provenance, compatibility and rollback evidence | ACTIVE GAP | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::PHASE_P_REAUDIT_V1` | `EP::P_TRANSPORT_V1`; `EP::P_QUEUE_V1`; `EP::P_NEUTRAL_V1`; `EP::P_RELEASE_V1` | Zero active migration gaps or explicit approved retirement | PLANNED / incomplete | REQUIRED_BEFORE_STANDALONE_VERIFIED |
| `EP::PD_INSTALLED_PRODUCT_GOLDENS_V1` | `EP::PHASE_P_REAUDIT_V1`; `EP::P_INSTALLER_V1` | Installed Managed, Genesis and armed-retry Golden evidence | BLOCKED_BY `EP::PHASE_P_REAUDIT_V1` | REQUIRED_BEFORE_STANDALONE_VERIFIED |
Expand Down
Loading
Loading