Story: Bootstrap polish
This page documents a story in Sprint 06. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Polish the bootstrap surface introduced in sprint 05: move the runtime context to the database, remove the bootstrap-mode flag from context now that it isn't needed at runtime, and add manifest-level password-validation control.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 06 |
| Now | Completed 2025-12-13. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2025-12-13 |
Acceptance
- Context schema persisted in Postgres; rehydrated on startup.
- Context carries no bootstrap flag.
system.disable_password_validationreadable from the manifest.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Move context to database | DONE | 2025-12-13 | 2025-12-13 | The runtime context (session, user, request metadata) lived in memory; persist it to the database so it survives restarts. |
| Remove bootstrap mode from context | DONE | 2025-12-13 | 2025-12-13 | Bootstrap mode is a startup-only concern; remove the runtime context's awareness of it now that the workflow handles itself. |
Add system.disable_password_validation to manifest |
DONE | 2025-12-13 | 2025-12-13 | Surface password-validation control via the system manifest so dev environments can disable it without code changes. |
Decisions
- Bootstrap state stays inside IAM
- other components have no business knowing about bootstrap mode.
See also
- Authentication bootstrap follow-up (sprint 05) — predecessor.
- Implement database configuration (sprint 05) — sibling work in the configuration thread.