76 lines
3.1 KiB
Markdown
76 lines
3.1 KiB
Markdown
---
|
|
id: release-deployment-matrix
|
|
name: Deployment matrix final pass — all three engines, release text
|
|
status: pending
|
|
depends_on: [release-n1-growth-posture]
|
|
scope: moderate
|
|
risk: low
|
|
impact: component
|
|
level: implementation
|
|
tags: [wave-8, docs, deployment]
|
|
---
|
|
|
|
## Description
|
|
|
|
The plan's wave-8 "deployment matrix final pass (across all three
|
|
engines now)": `docs/architecture/deployment.md` read row-by-row
|
|
against the three implemented engines and finalized as release text —
|
|
the document is ADR-016's honesty carrier (with the engine crates'
|
|
own docs), so every row must be true as implemented, not as designed.
|
|
|
|
1. **Row-by-row verification**: host semantics, connection budgets
|
|
(SQLite writer/reader/watcher; pg `max_size` + the non-pooled
|
|
listener; mem's none), durability knobs, TLS posture (v1),
|
|
toolchain/platform notes (incl. the mem wasm32 row), consumer-
|
|
obligation notes on engine options, and the latency profile's
|
|
"indicative, POC-measured" honesty (POC-measured numbers published
|
|
as indicative — confirm the caveat text is still accurate or
|
|
refresh it against the contract suite's existence).
|
|
2. **The env-variable boundary pin** (review 003's explicit
|
|
re-check-at-prepublish item): re-run the no-env-in-production grep
|
|
across the workspace (review 003 §Env-variable boundary has the
|
|
method + the prior result), confirm every `env::var` read still
|
|
lives in a test target, and pin the boundary in one sentence in
|
|
deployment.md (and the engine specs if the sentence belongs there
|
|
too): "env reads are harness-only; production configuration is the
|
|
opts-constructor surface."
|
|
3. **Fold N-1's outcome**: the growth-posture acceptance
|
|
(`release-n1-growth-posture`'s record) lands in the matrix's
|
|
durability/growth text.
|
|
4. **The mem rows' final honesty check**: ADR-024 landed them at
|
|
adoption; the wave-6 gate read them true — this pass re-reads them
|
|
as release text (ephemerality, isolation, wasm toolchain note).
|
|
5. **Release-text quality**: the document should stand alone for a
|
|
deployer sizing any of the three engines — no dangling references
|
|
to waves/tasks/POCs that a consumer wouldn't have context for
|
|
(POC-measured caveats stay, internal task pointers go).
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Every deployment.md row verified true as implemented across the
|
|
three engines; corrections landed
|
|
- [ ] The env-boundary grep re-run (result recorded) + the boundary
|
|
sentence pinned in deployment.md
|
|
- [ ] N-1's acceptance folded into the growth/durability text
|
|
- [ ] The mem rows re-read as release text
|
|
- [ ] No internal-task/wave pointers remain in the release-facing text
|
|
(POC-measured caveats excepted)
|
|
- [ ] Workspace gates green (docs-only expected)
|
|
|
|
## References
|
|
|
|
- docs/architecture/deployment.md (the document)
|
|
- docs/architecture/decisions/016-deployment-honesty.md (the carrier
|
|
mandate)
|
|
- docs/reviews/003-wave-5-general-review.md §Env-variable boundary
|
|
(the re-check item + method)
|
|
- tasks/release-n1-growth-posture.md (the input this pass folds)
|
|
- docs/architecture/engine-mem.md (the mem rows' spec source)
|
|
|
|
## Notes
|
|
|
|
> To be filled by implementation agent
|
|
|
|
## Summary
|
|
|
|
> To be filled on completion |