[efraespada]

Establish the Domus documentation foundation before application implementation. Eleven Draft SDDs record the owner's product decisions, Clean Architecture and Home Assistant contracts, with 82 normative requirements and 353 planned acceptance cases.

What changed

• Confirm Python/FastAPI, SQLite, one household per installation and a thin HA companion; select Lit/TypeScript/Vite, owned HA-coherent components, Storybook and Playwright after comparing Gateway and Symphonia.
• Specify role-default verification, actual-completion recurrence anchors, configurable successor release timing and advancement through nonexistent DST wall times.
• Make collaborative points configurable: conserved, rounded, decimal, full-performer and authorized manual modes retain immutable snapshots and actual award totals.
• Record adjustable task materials in the completion submission, configurable per task. Stock shortages save performed work and a pending-regularization intent without negative stock; reopening does not imply a physical return.
• Keep missed occurrences visible by default with a per-task policy. Recurrence edits preview changes and affect only unstarted future work while preserving active work, exceptions and history.
• Attribute participation and earned points to the actual-work period; required approval determines later spendability. Reversing already-spent awards can leave a negative balance that blocks new redemption while fulfilled rewards remain fulfilled.
• Strengthen cycle-based award uniqueness, atomic performer allocation, late-event handling, exact precision validation, receipt retention and current permissions on replay.
• Include camera/manual barcode entry, local matching and optional Internet product lookup; preserve manual shopping extras while deduplicating covered automatic needs.
• Include one automation engine with simple/default and optional advanced editors, durable replay-safe execution, simulation and traces.
• Confirm configurable administrator mapping, household role profiles/member exceptions and one-execution DST fold handling; retain current backend checks and grant provenance.
• Preserve both deployment targets, isolated Stable/Edge channels, meaningful tests from first code, 100% supported first-party coverage and the future project-owned CI Check workflow.

Validation

• All eleven drafts pass the unchanged original Copilot format and consistency functions, including canonical headings, numeric budgets, reciprocal case links and declared documentation paths. Local links, unchanged standard/template hashes and patch whitespace pass.
• The unchanged SDK catalog validator reports exactly 33 absent-evidence errors for proposed capabilities with no implemented entrypoints, code or tests. The supported bootstrap question is reported in 🐛🧑‍💻 - SDK proposed capability catalogs have no truthful greenfield SDD bootstrap route without implementation evidence copilot#777.
• The preceding head's progress assessment failed twice with assessment-invalid/agent.failed. Sanitized evidence is recorded in 🐛🧑‍💻 - Expose completed progress assessment validation failures instead of opaque agent.failed copilot#774 (comment). That workflow failure is distinct from the catalog limitation; current-head checks are independent.
• No application tests, coverage, browser acceptance or runtime implementation are claimed. Copilot, its installed resources and the existing gateway are unchanged.

Review notes

The latest owner-question batches are answered. Reopening a prerequisite preserves completed dependents/points with a review condition. Disablement stops new runs and later steps, lets already-started atomic commands finish and retains effects. Approved unfulfilled rewards without backing wait on a funding hold rather than being delivered or cancelled automatically.

Administrator mapping supports all_ha_administrators by default, setup_administrator and selected_ha_user alternatives. Predefined permission profiles allow household adjustments and per-member exceptions. Repeated local times execute once at the first appearance by default, with a household second-appearance option.

All SDDs remain Draft. Current HA identity/administrator proof, authenticated recovery, the detailed permission matrix, library/export interoperability, provider/device evidence and resource bounds still require engineering/security review and executable evidence. No unanswered question from the latest batches is treated as an accepted default.

This change contains documentation only; merge, release, deployment and application implementation remain outside this request.

Closes #2

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/domus~3

Documentation is deployed and generated using docs.page