KATLAS · Project Pathway

From use case to funded project pathway.

Sponsor brief, use-boundary triage, SOW-lite, budget gate and CTO handoff.

Lab Pathway does not stop at a demonstration. It helps turn an imagined AI use case into a scoped project pathway that a sponsor, COO, CTO, finance lead or university programme can review.

The output is not a fixed quote. It is a structured decision pathway: what should be explored, what should be built, what must be governed, what might cost money, who must approve, and what evidence is needed before deployment.

  1. /01

    Sponsor Brief

    Captures the project shape without requiring confidential data, credentials, API keys or production access.

  2. /02

    Use-boundary triage

    Determines how much governance is needed before the work can move toward build or deployment.

  3. /03

    SOW-lite outline

    Lightweight statement of work — scope, roles, assumptions, AI-use boundary, authority gates and receipts. Draft only.

  4. /04

    Budget pathway

    Indicative budget band and budget drivers. Not a quote.

  5. /05

    CTO Build Brief

    What must be built, bounded and tested. Handoff to delivery once the sponsor pathway is agreed.

  6. /06

    Evidence Pack

    Auditor- and procurement-ready artefacts bundled for sponsor, CTO, risk, DevOps, procurement and auditor review.

  7. /07

    Project Pathway Receipt

    Records how the idea moved from sponsor brief to scoping decision. Always SIMULATED unless live KATLAS signing is active.

Where the project starts

Many possible starting points.

A project may begin with a COO, department sponsor, CTO, innovation lead, university programme, risk lead, compliance owner, customer problem, marketing team, sales team, pre-sales team or delivery team.

Agentic AI means more people can now create content, workflows, prototypes, APIs, automations and technical artefacts. Lab Pathway helps convert that activity into a governed project pathway before cost, risk or technical debt accumulate.

Why this is faster

Faster than starting from scratch.

Lab Pathway combines rapid agentic app assembly with KATLAS / Cierge governance. The output is a previewable, sponsorable, budget-mapped project pathway — not another deck.

  • /01

    Agentic app templates

    Rapidly assemble operator consoles, scenario UIs and sponsor previews.

  • /02

    Hosted redacted demos

    Stakeholders can review a working synthetic demo before procurement or integration.

  • /03

    Remixable pathways

    Reuse scenarios, policy patterns and runbooks across sectors.

  • /04

    KATLAS / Cierge governance

    Custody, Authority and Receipts turn demos into accountable workflows.

  • /05

    Connector & policy packs

    Prebuilt connector patterns, source registers and policy templates reduce pilot friction.

  • /06

    Evidence pack export

    Auditor / procurement-ready artefacts help move from demo to paid pilot or MVP.

Step 1 · /01

Sponsor Brief.

Captures the project shape without requiring confidential data, credentials, API keys or production access.

No confidential data, credentials, API keys or production access are required.

Step 2 · /02

Use-boundary triage.

Determines how much governance is needed before the work can move toward build or deployment.

Safety consequence

1/5

Regulatory consequence

1/5

Financial / operational consequence

1/5

Data sensitivity

1/5

Autonomy level

1/5

Sustainability / resource impact

1/5

Indicated governance depth

GREEN

Green — exploratory playground

Synthetic only, no live data, no operational decision.

Step 3 · /03

SOW-lite.

Lightweight statement of work — scope, roles, assumptions, AI-use boundary, authority gates and receipts. Draft only.

Draft SOW-lite — for scoping discussion only · not a binding contract

Step 4 · /04

Budget pathway.

Indicative budget band and budget drivers. Not a quote.

Indicative budget bands

Budget drivers (select what applies)

Indicative budget pathway — not a quote. A binding budget requires a scoped statement of work and a separate engagement letter.

Step 5 · /05

CTO Build Brief.

What must be built, bounded and tested. Handoff to delivery once the sponsor pathway is agreed.

The sponsor brief explains why. The CTO Build Brief explains what must be built, bounded and tested.

Step 6 · /06

Evidence Pack.

Auditor- and procurement-ready artefacts assembled from the steps above. Bundles the project pathway into a shareable, reviewable package.

What an Evidence Pack contains

  • /01Sponsor Brief (this pathway)
  • /02Use-boundary triage result + scores
  • /03Draft SOW-lite outline
  • /04Indicative budget pathway
  • /05CTO Build Brief
  • /06Source register snapshot
  • /07Authority gate map
  • /08AI-use boundary statement
  • /09Receipt template + this pathway receipt
  • /10Disclaimers (synthetic only · indicative · not a quote)

Who reviews it

  • Sponsor / COO

    Confirms problem framing, intended impact and budget appetite.

  • Risk / compliance

    Reviews use-boundary triage and authority gates.

  • CTO / architect

    Reviews CTO Build Brief, source register and integration assumptions.

  • DevOps / security

    Reviews deployment assumptions, secrets handling and connector patterns.

  • Procurement

    Reviews budget pathway, drivers and engagement-letter route.

  • Auditor (where required)

    Reviews receipts, evidence boundary and verification state.

The downloadable Project Pathway Brief PDF below is the current rendering of the Evidence Pack — a starting bundle for the conversations above.

Step 7 · Project Pathway Receipt

Receipt the decision.

Records how the idea moved from sponsor brief to scoping decision. Always SIMULATED unless live KATLAS signing is active.

SIMULATED — NOT A LIVE KATLAS-SIGNED RECEIPT

Project—
Sponsor role—
Authority owner—
Indicative band—
TriageGREEN · max 1/5
Proposed pathwaySynthetic playground first
Evidence sharedSponsor-brief summary only
Evidence withheldConfidential data · credentials · production access
Next decision gateScoping review
Statussynthetic / playground
VerificationSIMULATED
Draft · Indicative · Not a quote

Continue

Pair the Project Pathway with the Operating Model.

Operating Model →Platform explainer →