Skip to content

Latest commit

 

History

History
263 lines (162 loc) · 13 KB

project-thread-record.md

File metadata and controls

263 lines (162 loc) · 13 KB

Reference: source map — project, Thread, and record

Verified-Against: 75e977b6 (2026-08-31).

Audience: agent · Diátaxis: reference · Kind: contract

Census of project ledger, Thread snapshot, brief, and record-reconciliation files. Not Workbench presentation and not CAS directory roots.

Index: workspace source map. Domain coverage stays on engineering domains.

Source map

Four-layer graph inventory (ThreadSnapshot, AnalysisGraph, BFF ThreadGraph, Graphology) with live dl05 examples for coherence review; not a Workbench screen

Project ledger adapters: baseline.from-approved-brief@1 executor, command runtime, cockpit-focus store, initial-baseline evidence validator. Brief tools stay under src/tools/. Not CAD/FEA

Read-only Thread/BFF projectors and post-projection enrichers (GET + SSE). Not command authority. Métier catalogs stay under cad/canonical and architecture/renderer

Outbound cockpit-focus ledger port. Other project ports remain flat under ports/out/

record.reconcile-uncertain-writer@1 proposal and accepted-write basis-release. record.seal-documentary-clause-response@1 closed clause-response grammar. Archive cascade math stays in domain/thread/thread-retirement.ts. Not CAD/FEA

Trusted executors for record.archive-lineage@1, record.reconcile-uncertain-writer@1, record.seal-requirements-brief-trace@1, and record.seal-documentary-clause-response@1. No WAL, no provider. Shared thread-write guard lives in adapters/shared/thread-write-basis-guard.ts

Canonical linked product state; schema 1.1 carries a non-empty validated AnalysisGraph while 1.0 remains provenance-only history

Exact previous-chain descendant proof. Not numeric revision, not latest. Shared by completed-dependency resolution and adapter lineage checks

Stable engineering activity, immutable work revisions and bound run attempts. The server stamps activityId; labels, timestamps and latest never group or select revisions

Exact selected dependsOn leaf for requiresDependsOnOperation. Planning issues and runtime resolution share this rule. No sibling inference

Named completed work artifact plus current-revision dependsOn wrapper. Runtime uses dependsOn + required operation; preflight review uses unique completed operation leaf then the same evidence resolver. Not an active-head label scan. Used by X07/X09/X11 structural selectors

Immutable project intent and execution-state contract

Generic draft source-tree aggregate: modules, files, versioned authoring attachments, exact predecessors, derived POSIX paths, mutation-id idempotency. Event /3.0, snapshot /2.0. Replay is pure. Not Thread, not admission

Append-only event adapter under state/local/project-source-workspaces/, composition, the fixed generic v1 attachment-role catalogue, and the product-navigation authoring attachment reader. Claim/publish fail-closed. Not a generic repository. server.ts shares one CaptureProductStructureTraversal and one workspace store with product navigation.

Project-scoped mutations and revision-anchored reads. File put reopens the exact AgentResourceReference before the event is accepted. Attachment put recrosses the current Thread tip and architecture-capture/4.0 unless the mutation id is already accepted. Not admission

Eleven MCP tools for the draft source tree and authoring attachments. grants: none. Optional captureRequest is stored inertly; Vertical 1 does not register it. Attachment roles are the fixed generic v1 catalogue only

Unique current Thread tip from the project ledger, plus the closed basis parse. Not latest. Shared by FEA reviews and CAD/compile command parsers

Living brief, questions, sourced answers and exact review contract

Application use case for project-from-intent and reviewed brief revisions

Read-only project_sensitivity_base_evaluation_review. Corrections return through project_resource_capture plus a successor workspace file revision; there is no corrected-admission review tool

Live from-zero script for a new project on the behave branch; lists harness refusals; does not replay dl05 or open make/buy

Behave continuation after FEA: join, fail-only correction, z*, reseal. DFM is the other branch. Historical dl05 r16 is UNLINKED

Canonical declared, inferred or observed engineering relations with exact evidence, distinct from Thread provenance; the authority-admission type is separate and not activated by analysis

Canonical AnalysisGraph index over validated assertions and exact semantic endpoints; no second relation dialect, provenance rewrite or authority

Agent MCP project framing and exact brief-confirmation tools

Startup-owned interactive or loopback-only local-YOLO gate table; auto-confirms positive brief/MRTR, queued-run cancel, work-item abandon, and reviewed registered human-only execute; never rejects; identity fixed as human/local-yolo:startup-opt-in

Public validation facade for project snapshots and exact Thread references. Structural parsing and invariant families live beside it under src/domain/project/validation/

Frozen YAML DAG authoring prototype (spec + engine, no production caller)

Pure selector for one exact, active, non-archived requirements component tip; shared by writer, executor and review

Authenticated command-origin contract shared by project use cases and their inbound execution boundary

Inward exact-run execution contract shared by the MCP tool, application dispatcher and structurally compatible server-owned executors

Outbound immutable project-revision persistence contract and optimistic-conflict error

Cross-process append-only live activity journal

Browser-safe running/fresh/failed MCP projections

Immutable local snapshot persistence

Tracked seed plus immutable active project revision store

Transactional application facade for reviewed project transitions, authority checks, idempotent replay and receipts. Command DTOs, policies and stage-owned transitions live beside it under src/application/use-cases/project/commands/

MCP command runtime and exact evidence readers

Operator recovery for a leftover ready work item after a completed successor. Not an MCP tool. Inspect by default; --apply writes through the command service. Task: recover:work-item-successor

Completion evidence existence and change gate

Application dispatch for exact reviewed operations through ports/in/project-run-executor.ts; concrete executors are wired only by the composition root

Generic trusted executor for record.archive-lineage@1: governed retirement cascade, gated by a human-approved decision sealing the exact thread-entity targets; no provider call

Trusted executor for the human-only record.reconcile-uncertain-writer@1: gates on human origin and an exact re-hashed MRTR; provider-did-not-write may release the basis, while write-effect-accepted creates a separate governed release decision; no provider call or ThreadSnapshot

Single fail-closed reconciliation grammar plus persisted human-ceremony verification for both outcomes

Provider-neutral extra eligibility for historical generic uncertain writes. Closed by default. The Chrono adapter lives under src/adapters/mechanics/chrono/

Exact 11-field accepted-write basis-release contract; validates canonical reciprocal blocker/decision state, recomputed proposal fingerprint, exact basis, and one matching human approval

Write-boundary lineage integrity. Exact descendant proof is domain/thread/thread-snapshot-ancestry.ts and is re-exported here

Agent MCP planning, elicitation, queueing and bounded execution; geometry preview depends only on its inward use-case port, not provider clients or CAS stores