dsh-factory-protocol

Host-independent records and pure algorithms for Factory.

The strict durable format contains workspace execution/title/worktree settings, optional metadata instructions, task nodes with optional blank-Session provenance, per-submission intake identity, and image-bearing discussion items, standard and per-project inbox flows, origin-tagged execution attempts, one-shot and friendly recurring schedules, per-run all-terminal Triage receipts/review timestamps, exact metadata-generation requests/results, mutation receipts, and bounded activity. Parsing rejects removed pattern fields, inconsistent project settings, flow/task membership, duplicate inboxes, malformed schedules, mutation hashes, operations, hunk paths, line totals, and commit order.

Agent observations and the scheduler lease are ephemeral SQLite records projected beside the document. FactoryArtifactMedia and its list/data requests are non-durable browser-review records: a branded media id plus a file revision selects one image or video under an exact task/run checkout's .artifacts directory without adding bytes to the Factory document. FactorySessionIntakeRequest gives each live blank Session composer submission a branded intakeId and consumes Run later or Flow intent into a draft in Emerging work, a generated flow root, or an existing-flow parallel/sequential/finalizer position. Repeating one intakeId is idempotent, while another submission from the same Session creates another task; FactorySessionIntakeResult returns the exact task id for redirect. FactoryTaskActionRequest carries optimistic lifecycle mutations, including permanent deletion eligibility enforced by the domain. validateTaskGraph() rejects missing, cyclic, cross-project, unsafe finalizer, and inconsistent flow edges. readyTasks() applies dependency and finalizer policies in Linear priority order; orderTaskGraph() provides stable dependency-first presentation. factoryRecurringCron() compiles structured local-time schedules for domain evaluation.