Request to code, on one pane

One system from the request to the code, and back.

A request arrives. PINKTURKEY works out what kind of work it is, what it touches, what it is likely to cost, and what the agent is allowed to know. What comes back is on the record. There is no second tool to re-enter it into.

Connect your repositorySee the governed context
  • One door for every kind of request
  • An estimate before the run
  • Only effective records reach the agent
CANONICAL RECORD GRAPH
REQRequirementv8 · accepted
DECDecisionaccepted
CTXContext Packsealed
EVDEvidencefresh
RLSReleaseready
A product view, not a brochure diagram

One requirement, and everything currently holding it in place.

The record on the left is a requirement. Everything on the right is what currently constrains it: the decisions still in force, the interfaces that implement it, the evidence that still counts. This is the view the agent is given a scoped copy of.

  • What it saysThe accepted requirement and the version that is currently in force.
  • What holds itDecisions, interfaces, tests and evidence, each connected explicitly rather than inferred.
  • What the agent getsThe same picture, scoped to the task, with superseded records left out.
Connect your repositorySee what governs now
Payments modernizationGoverned workspace
Pilot workspace
REQUIREMENTS12 current
REQ-0042 · VERSION 8

Verify subscription activation before capability becomes available

ACCEPTED

Business capability becomes available only after trusted provider evidence is reconciled with the account and workspace activation state.

OwnerProduct & Billing
CriticalityHigh
ChangedToday
CONNECTED DELIVERY CONTEXT6 current links
DEC-0017constrainsProvider-confirmed activation
API-0012implemented bySubscription activation command
VRQ-0028verified byActivation state evidence
RSK-0009mitigatesPartial commercial activation
The loop

Six steps, and no second system.

No single step here is novel. What is different is that they are one system, so nothing is lost between them and nothing has to be re-entered somewhere else to be tracked.

  1. Request

    A prompt, a bug report, a change request or an incident. All of them arrive the same way, so you do not have to decide in advance which system it belongs in.

    Where does work start?

  2. Interpretation

    The system reads the request and proposes what it is — a change to an existing requirement, a defect against released behaviour, a new objective. You confirm or correct it.

    What kind of work is this?

  3. Relation

    It connects the request to the records already in force: the requirements it touches, the decisions that constrain it, the parts of the codebase it will reach.

    What does this touch?

  4. Estimate

    Before anything runs, you see what the change is likely to cost in model spend and in scope, and which records it will put in motion.

    What will this cost?

  5. Governed prompt

    The agent receives the objectives, requirements, decisions and constraints that are currently effective for its scope. Superseded records are withheld, and the withholding is recorded.

    What does the agent receive?

  6. Code and record

    What came back is attached to the claims it serves. Anything it contradicted is raised rather than quietly overwritten.

    What changed as a result?
Go deeper

Three parts of the loop worth a closer look.

The loop above is the shape. These are the three places where the detail matters most.

01

What governs now

How a record moves between proposed, effective and superseded, and how authority is bound to a scope and a period rather than asserted once.

See what governs now
03

Evidence and release

How proof stays attached to the exact claim and version it supports, and expires when the system moves underneath it.

See evidence and release
Capabilities, with their real status

What is built, what is being built, and what is not.

Every capability below is listed as it actually stands. An item reaches Available only once it is in production and verified.

Records and authority

  • Record identity and immutable versionsAvailable
  • Typed relationships between recordsAvailable
  • Authority state: proposed, effective, supersededAvailable
  • Scope- and time-bound authorityAvailable
  • As-of queries against any past dateAvailable
  • Policy evaluation with recorded decision evidenceAvailable
  • Baseline capture and replayAvailable
  • Gap, debt and blocker trackingAvailable

The governed loop

  • Domain Hold — scoped blockingSchema is in production; the runtime path is the round in progress.Partial
  • Governed context: only effective records are sentIn build
  • One door for requests, changes and incidentsIn build
  • Interpretation and relation to existing recordsIn build
  • Cost estimate before the runIn build
  • What binds now — the working boardIn build
  • Jira and Confluence coexistencePlanned
  • Brownfield reconstruction from an existing codebasePlanned

This table is generated against the delivery plan rather than written for the site, which is why it names things that are not finished. If a capability you need is In build or Planned, ask before you subscribe rather than after.

Start where the problem is

Find out what is currently steering your agent.

Connect one repository. The first run returns the decisions, constraints and requirements that appear to govern it today, and asks you to confirm or retire each one.

Connect your repositorySee plans