Przejdź do treści

P098: Dependency Review

Date: 2026-11-07. Scope: documentation review only.

Parent: Alpha UI. Canonical tasks: delivery plan.

Current audit and exact scope

dependency-scopes.json defines the roots, included scopes, edge direction, normalization rules and derived delivery views. The scopes are:

  • engineering_foundation: the P098-002a contract/type/conformance slice;
  • local_primary: the first usable participant profile's delivery record;
  • independent_profile: the full independent-participant delivery record;
  • independent_with_follow_on: that profile plus the explicitly listed domain follow-on roots;
  • optional_web_observation: Web read/status without reviewed draft promotion;
  • optional_brainflow_synthetic: participant UI and owner adapter with synthetic source evidence only;
  • optional_brainflow_real: that UI plus selected real-device owner and route qualification, retaining the scoped P096-011a input;
  • optional_integrations: the optional Responsibility, Web observation/review and BrainFlow synthetic/real paths;
  • full_review: those scopes plus deferred editor/CSS and the complete P095 client migration (including remaining legacy routes).

dependency-audit.json contains generated counts for each scope, the expanded roots, full prerequisite graph, task-row provenance, source content digests, extraction-rule version and read-only view status. Its checks cover missing/duplicate IDs, cycles, owner direction, engineering/early-profile independence, 005a's early delivery, return without unrelated views and complete final scope. Additional checks prove that Web observation does not require finite original-backed promotion, synthetic BrainFlow does not require hardware qualification, and the real-device path does require its named owner/UI gates. Reviewed Web handoff uses the qualified common guided frame and ends at the receiver-owned unpublished draft/summary readback. It does not require Whisper publication, crypto/viewer integration, My rumors or the Memarium explorer. Onward contribution remains gated by P098-005b. Counts belong to this artifact, not manually maintained proposal prose.

The integration-seam review splits P098-002 and P095-013 into named subgates and adds optional owner/UI roots. Counts therefore describe changed graph scope, not implementation progress. New owner tasks have no prerequisite edge to P098. P098-002a depends only on P095-013a and accepted source-pinned contracts: supplied values, two executable examples and one test consumer. P091-016/P095-014 join at P098-002b. Full inventory, graph tooling, live configuration consumption, route migration, independent runtime and optional owner freezes/adapters are not foundation prerequisites. P098-017/023 retain their baseline outputs without optional P098-024–028 or the remaining legacy-route migration P095-013c. The independent session producer P095-012 uses the type and conformance contracts; it does not wait for migration of the local-primary or remaining legacy routes. Actual UI consumers still qualify their own restricted routes.

The 2026-11-07 review also removes serialization of P084-016/P096-019 behind P082-023 and P078-017 behind the Web observation DTO. Existing accepted schemas support parallel freezes; their actual adapters still join the completed P082 port or Whisper receiver and exact finite custody at runtime. The audit checks these absences as well as required runtime joins. Fewer prerequisite edges do not remove owner obligations or expand evidence scope.

This artifact was generated by a temporary review extractor, with a separate DFS checking the topological result. The extractor is not checked into the repository, so this is bounded review evidence, not completion of P098-011 or a claim that Make/CI can yet reproduce it. The declared input/rule file lets another extractor target the same graph. Full parser rejection/fixture coverage and the stable report-generation command remain P098-011 work.

When implemented, P098-011 must generate the same named scopes and preserve the scope/source/algorithm identities. It must distinguish prerequisite edges from consumer links, accepted-contract boundaries, retired task mentions and view membership. Test full suffix IDs such as MSG-ONB-001c-04, historical bare 002 resolution in P098-008, ranges, qualified outputs and ambiguous/unparsed input. Current P098 rows use full prerequisite IDs; views never gain a mutable status. Backtick-wrapped task IDs/statuses remain ordinary tracker values. Preserve accepted-output qualifiers such as the selected P096-011a tuple separately from whole-task completion; an edge alone proves neither that the scoped evidence exists nor that the owner task is complete.

Historical result

The retained historical audit data records the last earlier root set and graph. It mixed all then-declared P098/owner task roots with named follow-ons; it was not the closure of P098-023 alone. Its original source snapshots were not retained in the repository. Earlier prose totals are superseded as scheduling evidence, and numerical agreement with this broader historical graph is not required for a differently named closure.

The current root file removes that ambiguity prospectively. This review cannot reconstruct someone else's root/rule choices from their totals alone and makes no claim that a different extractor was incorrect.

Ownership and limits

P098-019–021 are retired task IDs, represented by communication, rumors_guided and memory views in the scope file. Their status is derived from required output rows; no owner or implementation task waits for a view. Existing owner/task status and evidence qualifications remain authoritative. Schema or fixture conformance never substitutes for participant runtime, browser/native or release evidence. The optional views also derive status from their own output rows and add no mutable coordination tasks. The former P078-016 operator-provenance qualification keeps its ID and scope; the new participant handoff is P078-017/018.