Micro-to-scale engagement journey
From one bounded handoff to a governed role network.
Five stages. Each defines what you contribute, what KATLAS contributes and the reusable assets you keep. Indicative planning bands help frame effort — they are not commitments.
Frame the governed handoff
Purpose. Identify one consequential event and the smallest practical role network.
- 2–4 key stakeholder conversations
- Current workflow and pain-point explanation
- One named event
- Agreement on the accountable roles
- Role and responsibility map
- Custody / authority / receipt analysis
- Initial protocol and evidence-boundary hypothesis
- Target demonstrator brief
- Role Network Blueprint
- Authority matrix
- First lifecycle event
- Evidence-boundary map
- Recommended Cierge Lab scope
Indicative planning band: 2–3 weeks.
Prove the governed pattern
Purpose. Create a realistic synthetic demonstrator for one lifecycle event.
- Confirm role responsibilities
- Validate synthetic scenario
- Review the authority / policy model
- Nominate demonstrator audience
- Cierge journey
- Role wallets / role-node representation
- Policy and authority model
- Synthetic evidence references
- Public-safe receipt journey
- Presentation and walkthrough narrative
- Sponsor-facing sandbox
- Role model
- Event sequence
- Governance receipt model
- Structured data / integration context
- Acceptance criteria and deployment pathway
Indicative planning band: 4–6 weeks.
Demonstrate separate accountable roles
Purpose. Show the governed workflow across separate role identities and devices.
- Nominate 3–5 accountable roles
- Provide controlled test participants
- Agree minimum evidence and authority boundaries
- Participate in a guided multi-device walkthrough
- Separate role-node configurations
- Institutional Role Wallet setup
- Role-to-role protocol prototype
- Cross-device workflow
- Governed receipt and public-safe observer view
- Distinct role identities
- Multi-device role demonstration
- Protocol state model
- Evidence-disclosure schedule
- Pilot-readiness findings
Indicative planning band: 6–10 weeks, depending on participant availability.
Connect one real operational boundary
Purpose. Connect the governed pattern to one controlled system-of-record or execution boundary.
- Nominate the first system owner
- Confirm access and security requirements
- Define a limited integration boundary
- Agree operational acceptance criteria
- Adapter design
- Integration and test harness
- Production-oriented policy pack
- Operational receipt model
- Deployment and assurance support
- Controlled adapter integration
- Live or production-adjacent governed handoff
- System-specific acceptance evidence
- Operational rollout recommendation
Indicative planning band: 10–16 weeks, subject to system access and external dependencies.
Reuse, expand and license
Purpose. Operate and extend the role network across further workflows, organisations or product areas.
- Nominate network owner
- Onboard additional roles
- Agree governance and support model
- Prioritise reusable protocol patterns
- Role-node and protocol licensing
- Runtime governance substrate
- Protocol maintenance
- Adapter and integration support
- Security and version-management support
- Enablement and operating-model guidance
- Licensed KATLAS role network
- Reusable protocol catalogue
- Policy-pack versioning
- Receipt and evidence model
- Scalable onboarding framework
Commercial structure agreed separately; no pricing appears in this public pathway.
The first Cierge Lab is not a disposable proof of concept. It creates the assets that a governed role network is later built and licensed on.