Files
-Puter 005b26fa32 Slices 2-4: Work becomes executable
Domain primitives: versioned WorkDefinition/DesignPacket with risk, questions,
and approval gates; lifecycle transition table with invalidation rules;
Resolver (Run/Attempt/outcomes/CodingKitV0); provider-neutral HarnessRuntime
with normalized events and a deterministic FakeHarnessLive that always reaches
a terminal classification and never claims implementation.

Convex durable model: workDefinitions, workQuestions, workApprovals,
designPackets, workSlices, workRuns, workAttempts, workAttemptEvents tables;
broadened works.status union; generalized workEvents with optional signalId,
referenceId, and payloadJson. Authenticated commands for definition request/
save/revise/approve, question answer/withdraw, design save/revise/approve, and
simulated execution start/cancel/retry with leased attempts, checkpointed
events, and expired-lease reconciliation.

Private work-planner FLUE agent with proposal-only tools (definition, design,
question). Convex validates and stores every proposal; FLUE never approves or
advances Work.

Expanded Work card with Outcome, Design, and Build sections wired to the new
mutations. Slice 1 conversation and provenance preserved.
2026-07-27 22:52:14 +05:30
..
2026-07-19 02:46:47 +05:30
2026-07-19 02:46:47 +05:30
2026-07-19 02:46:47 +05:30
2026-07-19 02:46:47 +05:30
2026-07-27 22:52:14 +05:30
2026-07-19 02:46:47 +05:30

Convex Backend

Convex is the only application API used by web, desktop, and mobile clients. The active Slice 1 backend is intentionally limited to tenancy, projects, conversation turns, Signals, Work, and Flue's required persistence adapter.

Domain relations

  • organizations and organizationMembers own tenancy.
  • projects owns the single v0 Git source; projectContextDocuments stores repository context.
  • conversations, conversationTurns, conversationMessages, and conversationAttachments own chat admission and reactive history.
  • signals, signalConstraints, and signalSources preserve structured intent and exact evidence.
  • works, signalWorkAttachments, and workEvents own proposed Work and provenance.

The flue* tables are infrastructure tables required by Flue's persistence contract. They are deliberately separate from the product relations.