feat: prepare ARR for controlled public deployment
This commit is contained in:
11
.project-docs/80-commitments/commitments.md
Normal file
11
.project-docs/80-commitments/commitments.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# Commitments
|
||||
|
||||
Track future-facing memory: promised follow-ups, unfinished loops, timed checks, and restart points.
|
||||
|
||||
| Date | Commitment | Trigger / Due | Owner | Status | Next Action |
|
||||
|---|---|---|---|---|---|
|
||||
| 2026-07-29 | Deploy the stable public Web/MCP profile, refresh SuperAgent discovery and rerun the no-PII XML vertical slice | Before enabling real business XML upload | User: deploy/DNS/Secrets/platform save; Codex: verify the next E2E when asked | Pending user deployment | Follow `deploy/README.md`; require Web `processing_ready=true`, MCP unauthenticated 401 and authenticated one-tool discovery; rebind/save/publish SuperAgent against the stable domain, then require an MCP commit receipt plus matching Finance facts. |
|
||||
|
||||
## Use
|
||||
|
||||
Record only commitments that should affect future sessions. Routine next steps can stay in `30-worklog/current-state.md`.
|
||||
Reference in New Issue
Block a user