docs consolidation
This commit is contained in:
@@ -1,12 +0,0 @@
|
||||
# Orchestrator AirGap Prep — PREP-ORCH-AIRGAP-56-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Owners: Orchestrator Service Guild · AirGap Policy Guild
|
||||
Scope: Awaiting AirGap readiness; capture sealed-mode contract needs for orchestrator.
|
||||
|
||||
## Needs
|
||||
- Sealed-mode contract from AirGap controller (seal/unseal scopes, staleness fields).
|
||||
- Mirror bundle pointers to include with orchestrator jobs.
|
||||
|
||||
## Handoff
|
||||
Use as prep artefact; update once AirGap 56-001 contract is published.
|
||||
@@ -1,9 +0,0 @@
|
||||
# Orchestrator AirGap Prep — PREP-ORCH-AIRGAP-56-002
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Scope: Downstream of 56-001; needs sealed-mode staleness propagation.
|
||||
|
||||
## Needs
|
||||
- From 56-001: seal contract and bundle pointers.
|
||||
- Staleness propagation rules to orchestrator runs.
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
# Orchestrator AirGap Prep — PREP-ORCH-AIRGAP-57-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Scope: Dependent on 56-002; timeline events for AirGap imports.
|
||||
|
||||
## Needs
|
||||
- Event types/fields for bundle import timeline.
|
||||
- Alignment with AirGap mirror bundle IDs and staleness.
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
# Orchestrator AirGap Prep — PREP-ORCH-AIRGAP-58-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Scope: Dependent on 57-001; Evidence Locker integration for sealed mode.
|
||||
|
||||
## Needs
|
||||
- Evidence Locker bundle pointers and attestation requirements in sealed mode.
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
# Orchestrator OAS Prep — PREP-ORCH-OAS-61-001/61-002/62-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Scope: Telemetry contract inputs and OAS baseline for orchestrator APIs.
|
||||
|
||||
## Needs
|
||||
- Telemetry/contract inputs from sprint 150.A (not yet published).
|
||||
- OAS baseline for orchestrator host.
|
||||
- SDK generation targets (depends on OAS v1).
|
||||
|
||||
## Handoff
|
||||
Use as prep artefact for OAS 61/62 chain; update when telemetry inputs published.
|
||||
@@ -1,21 +0,0 @@
|
||||
# Orchestrator OAS Deprecations Prep — PREP-ORCH-OAS-63-001-DEPENDS-ON-62-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Owners: Orchestrator Service Guild · API Governance Guild
|
||||
Scope: Define deprecation headers/docs for legacy orchestrator endpoints once OAS 61/62 are finalized.
|
||||
|
||||
## Dependencies
|
||||
- Final OAS base (61-001) and discovery (62-001).
|
||||
- List of endpoints to deprecate and replacement mapping.
|
||||
|
||||
## Proposed contract
|
||||
- Add `Deprecation` header and `Link` rel="alternate" to new endpoints.
|
||||
- Update OAS with `deprecated: true` and description of replacement.
|
||||
- Include changelog section and example responses showing headers.
|
||||
|
||||
## Acceptance
|
||||
- Replacement map documented in this file and in `docs/modules/orchestrator/api.md` once OAS is regenerated.
|
||||
- Sample response with deprecation headers under `docs/modules/orchestrator/samples/orch-deprecation@draft.json`.
|
||||
|
||||
## Handoff
|
||||
Use this prep doc to satisfy PREP-ORCH-OAS-63-001-DEPENDS-ON-62-001. Update after 61/62 freeze; then mark task DONE and proceed with implementation.
|
||||
@@ -1,17 +0,0 @@
|
||||
# Orchestrator Pack-Run Prep — PREP-ORCH-SVC-41-101 / 42-101 / TEN-48-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Owners: Orchestrator Service Guild
|
||||
|
||||
## 41-101 needs
|
||||
- Envelope + DAL from 38-101 to register pack runs.
|
||||
- Storage schema for pack-run records.
|
||||
|
||||
## 42-101 needs
|
||||
- Stream contract from 41-101 (pack-run plumbing) to drive streaming.
|
||||
|
||||
## TEN-48-001 needs
|
||||
- Tenant context plumbing for job DAL/routes.
|
||||
|
||||
## Handoff
|
||||
Use as prep artefact; update when 38-101 envelope lands and DAL schema is fixed.
|
||||
@@ -1,11 +0,0 @@
|
||||
# Orchestrator Tenancy Prep — PREP-ORCH-TEN-48-001
|
||||
|
||||
Status: Draft (2025-11-20)
|
||||
Owners: Orchestrator Service Guild
|
||||
Scope: WebService job DAL/routes tenancy context prior to enforcement.
|
||||
|
||||
## Needs
|
||||
- Tenant context plumbing and RLS rules for job DAL/routes.
|
||||
|
||||
## Handoff
|
||||
Use as prep artefact; update once tenancy model decisions are finalized.
|
||||
Reference in New Issue
Block a user