Repository navigation
QDB Advisory v0: durable founder execution loop - #3
Draft
leadingproblemsolver wants to merge 2 commits into
Draft
leadingproblemsolver wants to merge 2 commits into
leadingproblemsolver wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Target state
Ship the smallest auditable founder-advisory execution loop for the Sophie/QDB use case:
interaction -> evidence -> state change -> decision -> commitment/experiment -> follow-up -> outcome -> next-session briefProduct boundary
Stack decision
apps/qdb-advisory/Current artifacts
apps/qdb-advisory/README.md— v0 execution contract, invariants, runtime flows, done-when gatesapps/qdb-advisory/db/migrations/001_core.sql— eight-table canonical state model + idempotency + derived overdue commitmentsImplementation gates
Acceptance boundary
Do not merge as complete until a raw session can traverse the entire closed loop with no manual database edits and zero hallucinated critical objects.