docs(docs): V1-1 contract approved, technical design for review
Owner ratified the V1-1 business decisions. The contract now records them as approved, adds the nomenclature, the proposed SQL schema, RLS, RPCs, technical limits, journeys and test plan, and lists the choices left for the owner. OPEN_QUESTIONS, plan, DOMAIN_MAP, README and CLAUDE.md follow.
This commit is contained in:
1 parent
5502617193
commit
a6346105f1
7 files changed
+1061
-381
No files matched your search
@@ -39,12 +39,12 @@ Q2):
|
||||
|
||||
Planned, not implemented (roadmap in
|
||||
`docs/development/IMPLEMENTATION_PLAN.md` §0): V1-1 clients and animals (its
|
||||
contract awaits the owner's ratification), V1-2 sheets served from Supabase,
|
||||
V1-3 bilans stored in the cloud with history, V1-4 stored PDFs and authorised
|
||||
sharing, V1-5 mobile and accessibility pass; then professional verification,
|
||||
cabinets, entitlements, agenda, public site and the rest of the plan. Nothing
|
||||
on `develop` authorises a release: the release readiness track (TODO RR-1 to
|
||||
RR-10) comes first.
|
||||
business decisions ratified, technical design awaiting validation), V1-2
|
||||
sheets served from Supabase, V1-3 bilans stored in the cloud with history,
|
||||
V1-4 stored PDFs and authorised sharing, V1-5 mobile and accessibility pass;
|
||||
then professional verification, cabinets, entitlements, agenda, public site and
|
||||
the rest of the plan. Nothing on `develop` authorises a release: the release
|
||||
readiness track (TODO RR-1 to RR-10) comes first.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in new issue
Block a user