Product-to-Engineering handoff
Roover Homeowner Kernel v2.1
One concise, architecture-neutral Product contract for Engineering kickoff.
Independent v2.1 QA passed · approved for Engineering handoff/review · not production implementation/deployment
Start here
Kernel ContractObjective, 24 visible states, stable cards, truth, authority, fallbacks, priorities, and build sequence.
Product AcceptanceHuman-readable Given/When/Then catalogue. Declarative and not executed.
Declarative ManifestModest machine-readable mirror. Explicitly not an executable state engine.
Source BoundariesDecision authority, bounded source extracts, supersession, and fixture/live limits.
Frozen reference and evidence
Frozen hosted prototype24-beat fixture reference through booked visit and Activity.
Independent QA receiptFrozen fixture inspection tied to the exact prototype SHA.
Behavior receiptMachine-readable evidence from the frozen fixture review.
Structural package checks
Manifest schemaJSON Schema for the declarative Product mirror.
Validation receiptSchema, IDs, references, acceptance parity, links, and exact SHA only.
Validator sourceSmall auditable structural checker; no Product scenario execution.
Proof boundary
The prototype proves fixture visuals and interactions only. It does not prove live integrations, production writes, security, notifications, deployment readiness, or the later site-confirmed outcome. Engineering must map current architecture and convert the acceptance catalogue into executable tests.