kstrl atlas

A generated map of what the parts of kstrl are and what they are to each other: 53 components, 68 flows, seven layers. Built at ba6b182fbb.

Layer
Show
Zoom
Journey
GITHUBissues in, pull requestsout, polled never pushedFACTORY PROCESSone process; every decision is codeOPERATORone person, on the loopCONTROL DIRECTORYXDG state outside the tree;the governor the agent...AGENT CLIsubprocess in its ownprocess group; killed on...WORKTREEthe only tree the agent maywrite1INTAKE2PLAN3BUILD4DECIDE5MEASURE6SHIP7OBSERVE8LEARN9TRUSTServeDaemonthe daemon that admitsworkGitHubIntakethe issue readerWorkQueuethe queueSpendLedgerthe spend ledgerInboxthe decisions waiting foryouFlowControlthe open-PR boundSteeringyour PR comments, readbackArchitectthe planner that attacksthe specManifestthe component graphPRDwhat done means, per storyFeedforwardwhat the agent is toldbefore it startsKnowledgeInjectorfacts from earliercomponentsRetryContextwhat failed last timeEngineerLoopthe inner loop around theagentAgentAdapterthe wrapper around thecoding agentBreakerthe stall detectorPathGuardthe scope fenceOperatorContextyour standing instructionsMechanicalVerifierthe checks that need nomodelFailureParserstool output turned intotargetsReviewerthe second opinionSecurityReviewerthe security opinionContractTesterthe integration checkFixturesOraclethe answers the agentcannot rewriteAdequacyGatethe check on the teststhemselvesPolicyEnvelopethe written rules for amergeFindingsthe error signalCalibrationthe check on the checkersSenserun any check by handPipelinethe decision per componentSchedulerthe decision per runHumanCheckpointthe pause before a mergeConfigurationthe settings every loopruns onWorktreesone working copy percomponentPullRequeststhe mergeDistillerwhat was learned about theartifactDampenerthe regression guard onevery PRReleaseStagethe deployAutonomyLadderhow much the factory maydo aloneReplaywhat the ladder would havedoneStateDirthe governor's own files,out of reachSafeModeis the factory degraded,and whyHealthTrendingis the factory gettingworseEvolutionJournalthe record of everyoutcomeProposalssuggested harness changesPlaybooklessons shared acrossprojectsRuntimeSignalswhat production saysEventBusthe event streamReducerthe current state, rebuiltfrom eventsDashboardthe live viewProgressLogthe older event log, keptcompatibleLinearMirrorthe tracker mirrorCLIthe ks commandOperatoryouGitHubIssuesissues, the way inGitHubPRspull requests, the way outCodingAgentthe coding agent itselflabelled issuequeue itemnext ready itemadmission verdictopen-item capfactory runspeccomponent DAGstories + criteriaresolved config + timeoutsready componentsworktree per componentmax_iterations, sleep, prompt pathscomputed contextfactsfailures from last attemptpromptstdin promptstream + COMPLETE markernext failing storypasses flag (a claim)stall verdictscope verdictLoopResultworktree + PRDdiff + criteriadiffenvelope verdictadequacy findingsfixture resultscheck resultsraw tool outputstructured failurescriterion verdicts + concernsvulnerability findingsthe error signalretrypassed diffdurable factsmergepull requestmerged tiersbreaker component to resetcheckpoint / policy exception / budget overrundiff, findings, costapprove / reject / retryparked merge gatekstrl.toml, env, flagsrun outcomeflag bundle (withhold only)violation -> demotionregression (R10.11)autonomy.jsonspend.jsoninbox.jsonlcomponent outcomes + signaturesrecurring patternsexperiments.tsvtyped eventstyped eventsv1 mirrorevents.jsonlRunStateks statusfailures, budget haltsboard, checkpoint modalapprove / reject / snoozepromote with ack

Scroll to zoom, drag to pan, click a component to frame it, Escape to go back.

Work Measurement Feedback You Trust Learning Record built part built planned actsmeasures

Fill is build state, derived: a component is built when the entry named in the model exists in the modules named. Every line carries what it moves and is coloured by the layer it belongs to. Click a component; press Escape to clear it and return the view; arrow keys step a journey; double-click a region's name to frame the region. Text is drawn at 11px and never smaller: at Fit it is scaled down, and zoom brings it back.

Components by region; click one to focus it

1INTAKE

2PLAN

3BUILD

4DECIDE

5MEASURE

6SHIP

7OBSERVE

8LEARN

9TRUST

·OUTSIDE THE FACTORY

Invariants the rules the chips in the panel point at

  1. H1: AI-generated code is never gated by AI self-review.
  2. H2: any adversarial prompt-body change re-runs calibration and records the delta.
  3. H3: prompt version and snapshot hash move together in one diff.
  4. H4: every done claim states what was tested versus assumed.
  5. Doctrine: integrate at the edges, build only thin middles.
  6. Doctrine: enforcement reads artifacts, never agent self-report.
  7. Doctrine: autonomy is earned, bounded, revocable; the bundle may only withhold.
  8. Doctrine: no assumed numbers; advisory first, graduate on the operator's judgement.
  9. Doctrine: the human is a role, not a bottleneck; boundary conditions route to the inbox.
  10. Doctrine: the first-class phase count is frozen; new evaluators land inside a phase.
  11. Doctrine: new outcome surfaces reuse the shared disposition; existing enums are not retrofitted.
  12. Loop rule: what acts never measures its own result (a measurement written by the actuator is not a measurement).
  13. Loop rule: every component runs by hand first; a sensor reachable only through a factory run cannot be tuned.
  14. Record rule: the filesystem is the event bus; sinks are observability, never control flow; the dashboard is a view.
  15. Trust boundary: control state lives outside the agent-reachable tree; unreadable control state fails closed.