4.7 KiB
4.7 KiB
Proposed factory dependency map
Date: 2026-09-08. This is a source proposal for acceptance sequencing. Actual owner task statuses remain in their repositories and the derived Hub. Stage/receipt is not inferred from the existence of a message or package.
| Project gate | Supplying record(s) | Current return / next evidence | Factory effect |
|---|---|---|---|
| T03 identity admission | KEY-WP-0013-T02; platform custody record to be resolved through the existing Glas request | Two service clients and protected consumer delivery remain unproven. Tenant choice is resolved. Identify the exact admitted custody record; do not substitute a generic database lane. | Blocks approval service acceptance |
| T03 audit admission | AUDIT-WP-0009-T03/T09; APPROVAL-WP-0002-T01 | Evidence kind is implemented; sender scope/secret policy and credential admission need owner returns. T09 is already high priority/progress. | Blocks approval startup |
| T03 approval | APPROVAL-WP-0002-T01/T03/T05 | Published image is pinned. Latest recorded production review found no deployed service. Need identity, audit, rollout, claim/consume and restart/restore receipts. | Blocks native credential action |
| T03 credentials | SECRETS-WP-0009-T03; SECRETS-WP-0007-T04 and SECRETS-WP-0008-T02/T06 as applicable | September 7 decision-path proof resolved digest normalization; remaining external dependency is the approval claim endpoint. Need real scoped activation/delivery evidence. | Blocks paid real-model proof |
| T04 runtime/profile | SAND-WP-0015-T04; GLAS-WP-0012-T02–T06 | Pinned startup candidate and synthetic transport exist. Need protected placement, native credentials, real model, exact binding, teardown and negative evidence. | Blocks current local profile readiness |
| T05 worker | REINAH-WP-0003-T05/T06; ACTIVITY-WP-0032-T05, ACTIVITY-WP-0035-T08, ACTIVITY-WP-0036-T04 | Queue and repository boundaries exist; current source heartbeat correction needs deployed natural trace and controlled late-close evidence. | Blocks governed production lane |
| T05 placement | railiance-master admission contracts; concrete runtime/reef owner record selected in T01 | Existing user-service worker on railiance01 is the starting point. Require explicit ownership and admitted profile/credential/recovery contract for this host. | Blocks claim that the local proof operates on Railiance |
| T06 delivery | Chosen source repo record and consuming repo record selected in T01; existing forge/enablement contracts | No existing end-to-end HelixForge factory acceptance owner was found. Adopt bounded useful-change/release work, with independent tests and actual consumer. | Blocks useful factory result |
| T07 recovery | REINAH-WP-0003-T05; RPF-WP-0038-T04 and actual pilot workload/package owner | Restore demonstrations exist; scheduled caller, inventory/retention and current worker/pilot recovery still need exact coverage. | Bounds operating readiness |
| T08 value/load | HelixForge acceptance; UPC-WP-0003 as receiving context | No current fourteen-day factory delivery/load evidence was established by this assessment. | Blocks repeatability claim |
GLAS-WP-0015 is the existing owner-handoff coordinator for T03/T04. The factory project consumes its results and adds the software-delivery/operating acceptance that it does not own. Do not create parallel identity/audit/runtime coordination.
When adopting the map, record canonical task IDs, accountable contact, required receipt, source revision and next review condition in each owner handoff. Set structured dependency fields/edges only with the supported source/projection semantics; do not invent an API convention or overwrite source UUIDs.
Separate lanes retained outside the factory critical path:
NK-WP-0033/0034andRPF-WP-0027: known incident/verification closure. Resolve impact on the proposed privilege boundary before expansion; ordinary incident priority is not displaced by factory WIP limits.RMASTER-WP-0020-T08: retained CoulombCore cleanup, with recovery and explicit destructive-approval gates. It is not a prerequisite to installing the factory.RMASTER-WP-0020-T09,RPF-WP-0025,RAPP-OPENBAO-WP-0002,NK-WP-0032: public listener/private login migration. Preserve existing requirements; do not merge it into native service delivery unless an owner demonstrates dependency.STATE-WP-0079,CORE-WP-0010, relevantHUB-*andRAPPCOREHUB-*work: staged hub migration, with receiver and quiet-window gates. Keep existing coordination operational while the factory consumes stable contracts.CUST-WP-0038, ThreePhoenix HA, enterprise federation, broad repository renames, extra rein/model profiles and publication campaigns: separate benefit decisions; no blanket factory dependency.