The grounding layer beneath the whole pipeline. The sharper your org context, the sharper every downstream judgment.
Why Organization Context
Every agent decision is made against a backdrop the org already knows but rarely writes down. Organization Context captures that backdrop once -- who decides, how teams hand off, what risk the org will tolerate, what would quietly make delegation fail -- and feeds it into every stage that needs it. It is not a stage you complete and leave behind; it is the foundation the pipeline stands on, and it is read continuously by discovery, prioritization, and Delegation Readiness.
How to Capture It
1
Open Organization → Context
Each context type has its own card. Add as many entries as you need -- they are versioned and can be toggled active/inactive.
2
Write or Upload
Enter content directly, or upload an org document (org chart, policy, interview transcript). Only active entries are injected downstream.
3
Let It Flow
From there, context is read automatically wherever it is relevant -- you do not paste it into each stage. Update it once and every stage sees the new version.
Operating & Brand Context
Discovery
Company Profile
Organizational background, injected into discovery interviews.
Discovery + Scoring
Strategic Goals
Injected into discovery and into portfolio scoring for strategic alignment.
Build
Brand Guidelines
Injected into build synthesis for tone and voice consistency.
Discovery + Design
Org Chart
Used for stakeholder mapping in discovery and design.
Evaluation
Governance Policy
Pre-populates the evaluation governance step with org-level policies.
Evaluation
Evaluation Criteria
Default criteria applied to all new evaluations.
Discovery
Stakeholder Interviews
Interview transcripts, stakeholder profiles, and KPI extracts from listening tours.
Delegation Readiness Context
These five types map directly onto the five Delegation Readiness dimensions. They are the inputs that let the readiness assessment judge whether autonomy can be scaled responsibly -- and say "not ready" honestly when it cannot.
Readiness
Authority & Decision Rights
Who can act, override, pause, and own the stop button; decision rights and escalation paths.
Readiness
Coordination & Dependencies
Handoffs, upstream/downstream dependencies, and exception paths between teams.
Readiness
Tacit Knowledge & Human Repair
The judgment and exception-handling people currently absorb; expertise at risk of displacement.
Readiness
Exposure & Commitment Posture
Risk appetite, autonomy tolerance, and the commitments shipping autonomous agents creates.
Readiness
Systemic Blockers
Structural reasons delegation could fail here -- unowned stop button, coordination debt, unaccounted human repair.
Where Context Is Read Across the Pipeline
Capture context once; each stage pulls the active entries it needs.
RDY
Delegation Readiness
Reads Authority, Coordination, Tacit Knowledge, Exposure Posture, and Systemic Blockers -- plus departments and the portfolio -- to produce the verdict, dimension scores, and action items.
DSC
Discover
Injects Company Profile, Strategic Goals, Org Chart, and Stakeholder Interviews into the discovery interview so the opportunity brief reflects the real organization.
DSN
Design
Uses the Org Chart for stakeholder mapping when shaping the PRD and architecture recommendation.
BLD
Build
Pulls Brand Guidelines into build synthesis so generated artifacts match the org's tone and voice.
EVL
Evaluate
Pre-populates the governance step with Governance Policy and applies default Evaluation Criteria to every new evaluation.
PRT
Portfolio & Prioritization
Strategic Goals feed portfolio scoring so the highest-alignment work rises to the top of the board.
One source of truth: update a context entry once and every stage above reads the new version on its next run. Inactive entries are ignored, so you can stage context without affecting live output.