frontend-patterns/docs/DependencyRequirements.md

# Requirements to unblock frontend-patterns work

Reviewed 2026-10-04 against local owner files. This is a dependency acceptance
contract attached to the existing FEP tasks, not an owner acceptance, runtime grant
or claim that another repo has received a handoff. Workplan files remain authoritative.
Tasks use `wait` for blocked work; plans use `blocked` when no currently available
implementation can meet their remaining acceptance. No new source study is warranted
solely to fill a comparison window. The paused navigation fixture stays paused.

## Cross-repository requirements

| Requirement | Blocked local task | Responsible surface / live record | Required return before moving forward |
| --- | --- | --- | --- |
| Hosted discovery | FEP-WP-0008-T01 | reuse-surface hosted federation; credential custody railiance-platform/OpenBao, route `reuse-surface-hub-write-token` | Authorized registration of `capability.infotech.frontend-pattern-language`; anonymous/consumer lookup returns the exact entry, stable raw index and pinned release citations. Retain registration/readback evidence and owner revision. A prepared YAML entry or 404 is insufficient. |
| Actual consumer and common hook | FEP-WP-0008-T01/T02 | the-custodian/repo-seed common template owner plus the selected consumer repository owner; no eligible consumer identified in the bounded October 4 search | Name an actual eligible task and revision, install query/read/cite/record plus automatic closeout/index commit via normal template rollout, and retain a pinned decision note. Do not enroll a finished example, fixture or invented task. Return the concrete native consumer task ID when one exists; no dependency ID is fabricated meanwhile. |
| Receipt collection and delayed outcomes | FEP-WP-0008-T02 | selected consumer producer; activity-core collector (ACTIVITY-WP-0040 is finished) | Authorized source enrollment with exact index/event digests; one real use plus linked inspectable outcome, explicit unknowns and producer assertions; automatic artifact refresh after 14 days and unknown after 30. Retain duplicate/collision/malformed and delayed-chain proofs. Local producer/helper and existing collector are implemented; their fixtures do not satisfy real use. Route an uncovered collector change to an owner live record before activation, rather than reopening finished work by implication. |
| Admitted execution and budget | FEP-WP-0008-T03 | glas-harness GLAS-WP-0012-T02–T05; prj-helixforge-factory HFACT-WP-0001; activity-core ACTIVITY-WP-0032-T05 | Owner returns pinned admitted profile/runtime, scoped read/write/test/commit/publication grants, protected provider route and enforcement of six calls / 40,000 aggregate tokens / 30 minutes before execution. Include duplicate dispatch, restart, denial, provider failure, separate review context and audit/usage receipts. The candidate profile `1.1.1` is unverified; no legacy fallback. GLAS-WP-0012 directly waits on SAND-WP-0014-T05 and SECRETS-WP-0009-T03. Existing source/synthetic proofs do not establish admission. |
| Standing publication and rollback | FEP-WP-0008-T03 | activity-core ACTIVITY-WP-0041-T02/T03; railiance-platform RPF-WP-0048-T02 | Exact narrowly bound release identity and approved autonomous scope; authenticated CI/review/health issuers, full current continuous-health interval, production transport/observer integration and retained failed-health rollback proof. Publish/read back the exact reference revision; refuse denied mutation and preserve previous versions. Broker source tests and the attended September repair are insufficient. |
| Reachable inference path | FEP-WP-0009-T02 | llm-connect service contract; ops-bridge owns a workstation tunnel when required; deployment stays with its platform owner | Supply a documented accessible service origin from this execution environment and an HTTP 200 `GET /health` with `status: ok`; record endpoint, timestamp and runtime/profile owner revision. Owner must also establish `custodian-triage-balanced` resolution, requested 1,400-output-token enforcement, aggregate authorized attempt ceiling and usable usage/error receipts. Health alone proves neither provider readiness nor caps. Historical finished LLM-WP-0006 establishes the internal service contract, not a pending restoration task or present workstation connectivity. A newly found routing/deployment defect needs a native owner live record before repair; FEP does not fabricate its ID. |

### Return format and local verification

For each return, retain the native owner task/workplan ID (or document that it is
not yet assigned), source commit and artifact digest, exact tested environment,
dated evidence locators, remaining limits and admission scope. FEP verifies the
specific required behavior before clearing its wait; an upstream `done` label alone
is insufficient. External source status may have changed since this review.

No messages, external workplan edits, consumer enrollment, deployment or secret
retrieval are implied by filing this contract. Credential requests first use
`warden route find/show`; keys never enter this repo, chat or State Hub. The user
can review these concrete requirements without approving a speculative workflow.

## Local evidence gates and remaining implementation

| Local task(s) | Required evidence / what can be done now |
| --- | --- |
| WP-0009 T01 | Actual independent human review of the existing masked pilot-01 worksheet, disagreements and adjudication. Model scores cannot supply it. Human review instructions and blank sheet are already prepared. |
| WP-0009 T02 | Packet/runner/scoring are implemented; all twelve authorized attempts are reserved and failed, with no answers. The health-only preflight is now implemented separately, preserving frozen bytes. Service restoration and a fresh explicit budget/new preregistered run identity are required; do not retry or reuse the old identities. |
| WP-0009 T03 | Independent ratings plus usable fresh replication, then evidence-based M1 pass/revise/defer. Remains wait. |
| WP-0003 T01/T02 | M1 evidence gate WP-0009 T03, then full six-stream comparison and contrasting walkthroughs. Bounded source/runtime preparation already exists; no useful consumer-led new question was identified. Full-contract/AT/human evidence cannot be invented. T03 editorial M2 review and T04 concrete recovery experiment remain done with limits. |
| WP-0004 T01 | M1 acceptance, then canonical validator/exporter. Existing preview validators/export do not confer canonical admission. |
| WP-0004 T02 | Canonical export WP-0004 T01 **and an accepted M2 assessment** after WP-0003 T01/T02; completed editorial WP-0003 T03 currently says revise/defer. Then freeze at least six unseen prompts and compare manual navigation, alternatives, abstentions and unsupported claims. Previously disclosed cases are consumed. |
| WP-0004 T03 | Completed held-out evaluation, then two contrasting pinned real repositories and M3 empirical review. No studies are fabricated to clear it. |
| WP-0006 T03 | Useful naturally arising comparable prospective cycles and explicit protocol/returns review from WP-0003 or consumer-led WP-0008. Largest group has two cycles, one with unknown effort. LEARN-0019 has no answers and is a separate failed protocol; it cannot be pooled to meet the trigger. |
| WP-0008 T03 | After the owner returns and actual consumer outcomes above: a real unassisted scheduled end-to-end cycle, natural monthly packet, retained failure/restart/rollback tests and exact publication readback. Natural reporting is verified; automatic editing is still unadmitted. |

## Health-only preflight implemented under WP-0009 T02

Run `make inference-preflight` or
`python3 scripts/inference_preflight.py --endpoint http://127.0.0.1:18081`.
The command sends exactly one bounded GET to `/health`, follows no redirects,
prints only sanitized status, performs no `/execute`, reserves no attempt and
exits nonzero for unreachable/invalid health. A sandbox loopback failure must be
checked outside the sandbox before declaring the service unavailable. This is a
preparation aid for a future newly authorized packet, not a change to replication-02's
frozen runner or a way to regain its spent reservations.