@eir-labs/coltrane 0.5.1 → 0.7.2

package/standards/product-design-v1.json

@@ -0,0 +1,122 @@
+{
+  "slug": "product-design-v1",
+  "domain": "product-design",
+  "status": "active",
+  "description": "The default product-design standard: a double diamond mapped onto the cognitive primitives without embellishment. Discover diverges (SENSE then INTERPRET); define converges (JUDGE, sealing a Plan); develop diverges again and builds (PLAN then CREATE); deliver converges (VERIFY). The two convergences are held by the same seat and the two divergences by different ones, so a widening pass is never marked complete by the seat that narrowed it.",
+  "agent_slugs": [
+    "john",
+    "bill",
+    "miles"
+  ],
+  "phases": [
+    {
+      "name": "discover",
+      "chairs": [
+        {
+          "role": "discover",
+          "agent_slug": "john",
+          "depends_on": [],
+          "input_contract": [
+            "design-question"
+          ],
+          "output_contract": [
+            "design-brief"
+          ],
+          "required_skills": []
+        }
+      ],
+      "intent": "First divergence. Hold the question open: observations with their locators, the audience segments it lands differently for, the needs the current state does not serve, the adjacent questions the exploration surfaced, and an honest statement of how far the exploration actually reached. Findings only \u2014 nothing is chosen here."
+    },
+    {
+      "name": "define",
+      "chairs": [
+        {
+          "role": "define",
+          "agent_slug": "miles",
+          "depends_on": [
+            "discover"
+          ],
+          "input_contract": [
+            "design-brief"
+          ],
+          "output_contract": [
+            "design-definition"
+          ],
+          "required_skills": []
+        }
+      ],
+      "intent": "First convergence, and the seam between the diamonds. Name the ONE problem the second diamond opens on, what is out of scope, the success criteria a stranger could check \u2014 and, explicitly, the problems the brief surfaced that this definition discarded, each with its reason. Sealed as a Plan because the definition sequences what follows."
+    },
+    {
+      "name": "develop",
+      "chairs": [
+        {
+          "role": "develop",
+          "agent_slug": "bill",
+          "depends_on": [
+            "define"
+          ],
+          "input_contract": [
+            "design-definition"
+          ],
+          "output_contract": [
+            "design-concept"
+          ],
+          "required_skills": [],
+          "preferred_skills": [
+            "structure-conformance"
+          ]
+        }
+      ],
+      "intent": "Second divergence, built rather than described. The concept states its mechanism step by step, names which success criteria it answers, and carries its tradeoffs and open questions \u2014 a concept presented as settled cannot be evaluated against the contest it hides."
+    },
+    {
+      "name": "deliver",
+      "chairs": [
+        {
+          "role": "deliver",
+          "agent_slug": "miles",
+          "depends_on": [
+            "define",
+            "develop"
+          ],
+          "input_contract": [
+            "design-definition",
+            "design-concept"
+          ],
+          "output_contract": [
+            "design-verdict"
+          ],
+          "required_skills": []
+        }
+      ],
+      "intent": "Second convergence. Measure the concept against the definition as sealed, criterion by criterion, and separate what was observed from what was reasoned about \u2014 most design criteria cannot be executed, so a verdict that does not say so overstates its own evidence. Where the concept is sound but the problem was the wrong one, the recommendation returns the run to the first seam."
+    },
+    {
+      "name": "approve",
+      "chairs": [
+        {
+          "role": "approve",
+          "agent_slug": "",
+          "human": true,
+          "depends_on": [
+            "deliver"
+          ],
+          "input_contract": [],
+          "output_contract": [
+            "Judgment"
+          ],
+          "optional_outputs": [],
+          "required_skills": []
+        }
+      ]
+    }
+  ],
+  "input_types": [
+    "design-question"
+  ],
+  "output_types": [
+    "design-concept",
+    "design-verdict"
+  ]
+}

package/standards/promote-v1.json

@@ -0,0 +1,41 @@
+{
+  "slug": "promote-v1",
+  "domain": "preview-deploy",
+  "status": "active",
+  "description": "A minimal promote stub — the third movement of software-delivery-v2. It declares preview-deployment in its input_types so the chart's movement-2 → movement-3 edge is a satisfied hard edge (R7), and its one chair reads the deployment_id from the sealed preview-deployment to promote it to production, sealing a deploy-verdict for the production build's terminal state. Its FULL phase graph is deferred by the sealed design (gig 0538105e names movement-3 as a contract boundary only, requiring its own design run); this file is built only to the extent the chart's honest edge and the approval gate before it require. The gate's Judgment is offered to this movement as a seed at runtime — the approver's decision lands in the production deploy's ledger ancestry — without being declared in input_contract, because declaring it as a standard input would make it an outside-need the chart has no edge to satisfy.",
+  "agent_slugs": [
+    "deploy-agent"
+  ],
+  "phases": [
+    {
+      "name": "promote",
+      "chairs": [
+        {
+          "role": "promote-preview",
+          "agent_slug": "deploy-agent",
+          "depends_on": [],
+          "input_contract": [
+            "preview-deployment"
+          ],
+          "output_contract": [
+            "deploy-verdict"
+          ],
+          "required_skills": [
+            "vercel-api"
+          ],
+          "supplies": {
+            "vercel_token": "env:VERCEL_TOKEN",
+            "vercel_team_id": "env:VERCEL_TEAM_ID"
+          }
+        }
+      ],
+      "intent": "Read the deployment_id from the sealed preview-deployment, promote that deployment to production through the Vercel promote API, and wait on the production build with the same bounded poll, sealing a deploy-verdict for its terminal state. STUB: the full promote phase graph is deferred to its own design run per the sealed design's boundary."
+    }
+  ],
+  "input_types": [
+    "preview-deployment"
+  ],
+  "output_types": [
+    "deploy-verdict"
+  ]
+}

package/standards/software-change-v1.json

@@ -0,0 +1,147 @@
+{
+  "slug": "software-change-v1",
+  "domain": "software-change",
+  "status": "active",
+  "description": "The default software-change standard. Read the material exhaustively, fix the direction, settle the structure, make the change, then say whether what was built is what was decided. The seams are deliberate: the seat that reads does not decide, the seat that decides does not build, and the seat that builds does not judge its own work. Only the reading seat holds a tool grant, and it is read-only \u2014 the change is emitted as reviewable content, never applied.",
+  "agent_slugs": [
+    "john",
+    "bill",
+    "miles"
+  ],
+  "phases": [
+    {
+      "name": "sense-context",
+      "chairs": [
+        {
+          "role": "read-context",
+          "agent_slug": "john",
+          "depends_on": [],
+          "input_contract": [
+            "change-request"
+          ],
+          "output_contract": [
+            "change-context"
+          ],
+          "required_skills": []
+        }
+      ],
+      "intent": "Read the material the change lands in, to the declared boundary and no further: entry points, the files the change plausibly touches, the checks that already cover the region, the conventions it must hold to \u2014 and the unknowns, which are part of the reading, not a failure of it. No decision is taken here."
+    },
+    {
+      "name": "frame-change",
+      "chairs": [
+        {
+          "role": "frame-change",
+          "agent_slug": "miles",
+          "depends_on": [
+            "read-context"
+          ],
+          "input_contract": [
+            "change-context"
+          ],
+          "output_contract": [
+            "change-decision"
+          ],
+          "required_skills": []
+        }
+      ],
+      "intent": "Fix the direction from the reading: scope, non-goals, stop condition, and the alternatives set aside with their reasons. Stated before any structure exists, so the structure is answerable to it. Settled for the run \u2014 later phases append observations, never revisions."
+    },
+    {
+      "name": "plan-change",
+      "chairs": [
+        {
+          "role": "plan-change",
+          "agent_slug": "bill",
+          "depends_on": [
+            "read-context",
+            "frame-change"
+          ],
+          "input_contract": [
+            "change-context",
+            "change-decision"
+          ],
+          "output_contract": [
+            "change-plan"
+          ],
+          "required_skills": [],
+          "preferred_skills": [
+            "structure-conformance"
+          ]
+        }
+      ],
+      "intent": "Settle the structure the change will be built through: ordered steps with explicit dependencies, the checks that land FIRST together with what each reports while the change is absent, the paths the plan commits to touching, and the tradeoff at every step where more than one structure would have served."
+    },
+    {
+      "name": "create-change",
+      "chairs": [
+        {
+          "role": "write-change",
+          "agent_slug": "bill",
+          "depends_on": [
+            "plan-change"
+          ],
+          "input_contract": [
+            "change-plan"
+          ],
+          "output_contract": [
+            "change-set"
+          ],
+          "required_skills": [],
+          "preferred_skills": [
+            "structure-conformance"
+          ]
+        }
+      ],
+      "intent": "Make the change the structure implies, as patch content plus the checks it introduces. Where the artefact left the plan, the departure is recorded with its reason \u2014 the same seat that settled the structure is the one accountable for saying where it did not hold."
+    },
+    {
+      "name": "verify-change",
+      "chairs": [
+        {
+          "role": "verify-change",
+          "agent_slug": "miles",
+          "depends_on": [
+            "plan-change",
+            "write-change"
+          ],
+          "input_contract": [
+            "change-plan",
+            "change-set"
+          ],
+          "output_contract": [
+            "change-verdict"
+          ],
+          "required_skills": []
+        }
+      ],
+      "intent": "Measure the change against the commitments as fixed, criterion by criterion: which acceptance criteria are unmet, where the scope drifted, and \u2014 separately and always \u2014 which checks could not be executed and were reasoned about instead. When the evidence does not reach the question, the verdict is insufficient evidence, not a pass."
+    },
+    {
+      "name": "approve",
+      "chairs": [
+        {
+          "role": "approve",
+          "agent_slug": "",
+          "human": true,
+          "depends_on": [
+            "verify-change"
+          ],
+          "input_contract": [],
+          "output_contract": [
+            "Judgment"
+          ],
+          "optional_outputs": [],
+          "required_skills": []
+        }
+      ]
+    }
+  ],
+  "input_types": [
+    "change-request"
+  ],
+  "output_types": [
+    "change-set",
+    "change-verdict"
+  ]
+}

package/venues/ci-deploy-room-v1.json

@@ -0,0 +1,28 @@
+{
+  "slug": "ci-deploy-room-v1",
+  "institution_slug": "quartet",
+  "flavor": "ci-deploy",
+  "description": "The room a change-to-preview arrangement is held in. It equips exactly what the movements need and nothing more: read-only filesystem tools so the reading and branch-sensing seats can read the working tree, and the Vercel REST origin so the deploy seat can build and poll — a ceiling, not a grant, so it can only narrow a seated agent's own charter, never widen it. The one egress door names api.vercel.com; the only credential class it admits is the Vercel token, filled at seat time from the environment. Ephemeral, because a room that stood between runs would carry one gig's branch state and warm credentials into the next.",
+  "equipment": {
+    "tools": [
+      "Read",
+      "Glob",
+      "Grep",
+      "WebFetch(https://api.vercel.com/*)"
+    ]
+  },
+  "doors": {
+    "ingress": [],
+    "egress": [
+      "api.vercel.com"
+    ]
+  },
+  "installs": [],
+  "credential_surface": [
+    "vercel-token"
+  ],
+  "lifecycle": {
+    "policy": "ephemeral"
+  },
+  "responsible_chair": "quartet.chair.responsible-officer"
+}

package/venues/empty-room-v1.json

@@ -0,0 +1,19 @@
+{
+  "slug": "empty-room-v1",
+  "institution_slug": "quartet",
+  "flavor": "ingest-empty",
+  "description": "The goods entrance. This is the room for reading third-party content — mail, chat platforms, web pages, vendor documents — and it is bare because bareness is the control. Untrusted text cannot be reliably separated from instruction by the model reading it, so the constraint has to be structural: it holds NO tools (not read-only tools; none), no egress door of any kind, no credential surface, and nothing installed. One ingress door names the single source it reads from. A chair seated here can do exactly one thing: emit a typed record of what it read, whose provenance says the content is untrusted and never instruction, into a spool a LATER phase drains from a different room — one that holds interpretation capability and no ingress from this source. Private data is absent (no credentials, nothing mounted) and there is no attacker-steerable exit (no egress, and the one write goes to a fixed engine-chosen destination the content cannot redirect), so two of the three conditions that make injected instructions consequential are structurally missing rather than argued away. What remains is the spool write itself, which is a channel: fixed destination, declared type, no attacker-chosen route. The claim is a BOUNDED residual channel, not the absence of one. Ephemeral because a room that persists between ingestions carries the previous ingestion's content forward into whoever sits here next.",
+  "equipment": {
+    "tools": []
+  },
+  "doors": {
+    "ingress": ["mail.example.com"],
+    "egress": []
+  },
+  "installs": [],
+  "credential_surface": [],
+  "lifecycle": {
+    "policy": "ephemeral"
+  },
+  "responsible_chair": "quartet.chair.responsible-officer"
+}