Examples

These are pre-authored Process Templates packaged as Scrydon Pack bundles (.scrydon-pack.tar.gz). Each one bundles a process flow alongside an ontology — download, inspect, then upload via /api/packs/import. Examples are not auto-installed; you opt in by importing the archive into your organization.

Compliance

ISO Quarterly Review

Drives the recurring quarterly review cycle for ISO 27001 (Clauses 9 + 10) and ISO 42001 (A.8 + Clause 10).

Stages: Plan & Schedule → Vanta Status Pull → AI Governance Metrics Review → Operational & Security Metrics Review → Engineering Gaps Status → Findings & Decisions → Sign-off → Evidence Sync to Vanta.

Personas: Compliance Lead · CISO · AI Governance Owner · DPO · Engineering Lead · Executive Sponsor.

Output: signed quarterly review report, improvement-log entries, evidence uploaded to Vanta.

Download iso-quarterly-review-1.0.0.scrydon-pack.tar.gz

ISO Yearly Review

Drives the annual ISMS + AIMS review. Sequences pen-test execution, IRP + DR tabletops, IR training, restore test, AI impact assessment per system, AIUC-1 delta review against the current release, peer-review log roll-up, formal management review, risk-register snapshot, and audit-pack sync.

Stages: Plan & Scope → Risk Register Snapshot → Penetration Test → IRP Tabletop Exercise → DR Tabletop Exercise → Restore Test Execution → IR Training Session → AI Impact Assessment per System → AIUC-1 Quarterly Delta Review → Peer Review & Expert Consultation → ISMS + AIMS Management Review → Audit-Pack Sync to Vanta.

Personas: Compliance Lead · CISO · AI Governance Owner · DPO · SRE Lead · Engineering Lead · Executive Sponsor · External Auditor / Pen-tester.

Output: BELAC stage-1 audit-ready evidence pack + management-review minutes.

Download iso-yearly-review-1.0.0.scrydon-pack.tar.gz

For the full walkthroughs, see iso-quarterly-review and iso-yearly-review.

Governance

AI Boardroom

End-to-end board-meeting lifecycle driven by six specialist AI agents. The pack bundles a process flow alongside a working ontology (BoardMeeting, BoardDocument, ActionItem Object Types) so tasks and actions can be queried as ontology nodes. Ships with a downloadable Helios Renewables Q1 2026 board pack so you can drive a complete walkthrough on a fresh org.

Stages: Preparation → Meeting → Post-processing.

Personas: Executive · Secretary · Board Member · AI Platform.

Output: signed board minutes, structured decisions, owner-assigned action items, archived evidence pack.

For the full walkthrough with the demo board documents, see ai-boardroom.

Download ai-boardroom-4.2.0.scrydon-pack.tar.gz

Defense & Security

NATO OODA

Six-stage OODA-loop process flow for multi-domain operations. The walkthrough uses a fictional NATO task force monitoring Eastern Mediterranean shipping for sanctions violations — Operation Aegean Sentinel.

Stages: Sense → Analyse → Fuse → Decide → Execute → Review.

Personas: Officer of the Deck · Intelligence Officer · Communications Officer · Legal Advisor (JAG) · Commanding Officer.

Output: signed after-action report, named-vote decision log, intelligence fusion product.

For the full walkthrough with the Aegean Sentinel scenario, see nato.

Download nato-1.0.0.scrydon-pack.tar.gz

Enterprise Implementation

SAP Activate Demo

End-to-end SAP S/4HANA Cloud implementation lifecycle following the SAP Activate methodology. The walkthrough uses a fictional retail chain — Northwind Retail Group — migrating 12 country instances from ECC 6.0 to S/4HANA Cloud Public over 18 months.

Stages: Discover → Prepare → Explore → Realize → Deploy → Run.

Personas: Project Director · Solution Architect · Business Process Owner · Basis Lead · Change Manager.

Output: go-live sign-off pack, ABAP code freeze, hypercare exit report.

For the full walkthrough with the Northwind Retail scenario, see sap-activate-demo.

Download sap-activate-demo-3.0.0.scrydon-pack.tar.gz

How to import an example

bunx @scrydon/sdk-authoring pack inspect ~/Downloads/iso-quarterly-review-1.0.0.scrydon-pack.tar.gz

curl -X POST "$AGENTIC_URL/api/packs/import?organizationId=$ORG_ID" \
  -H "Cookie: $SESSION_COOKIE" \
  -F "file=@~/Downloads/iso-quarterly-review-1.0.0.scrydon-pack.tar.gz"

Customising before upload

Most teams will want to tweak personas, due-offset days, or replace actionType: workflow entries with their own workflowIds. Three options:

1. Edit the manifest, re-build. Clone the example source from packages/sdk-authoring/src/process-templates/examples/<slug>/index.ts, edit, then bun run --cwd packages/sdk-authoring build:examples to rebuild every pack. Or assemble a hand-authored pack directory and bunx @scrydon/sdk-authoring pack build path/to/pack.json --outDir dist.
2. Fork the manifest in TypeScript. Author your own defineProcessTemplate(...) in your repo, copy-pasting the example as a starting point. Recommended when the changes are non-trivial.
3. Edit process-flow/manifest.json inside the archive. Extract → edit → re-pack with tar -czf. Quick for one-off tweaks; not recommended for ongoing maintenance.

The example manifests are versioned (package.version in both pack.json and the process-flow manifest) — bump that when you fork so your org tracks the divergence.

Adding a new example

To contribute a new example:

1. Create packages/sdk-authoring/src/process-templates/examples/<your-slug>/index.ts exporting a defineProcessTemplate(...) result.
2. Append it to exampleTemplates in examples/index.ts.
3. (Optional) If your example needs a real ontology, drop the ontology subdir under packages/sdk-authoring/src/packs/examples/<your-slug>/ontology/ and register it in ONTOLOGY_OVERRIDES inside scripts/build-examples.ts. Templates without an override get an empty ontology auto-generated at build time.
4. Run bun run --cwd packages/sdk-authoring build:examples — the script auto-discovers and packages every entry.
5. The archive lands at apps/docs/public/static/process-pack-examples/<slug>-<version>.scrydon-pack.tar.gz and is served by the docs site.
6. Add a row to the table at the top of this page.

The build script is fail-loud: if a manifest doesn't validate against its schema, the example is rejected and the build fails with the Zod path of the violation.

What's NOT in an example

Pack bundles are pure data — they cannot include executable code. Custom logic is referenced by workflowId against system or organization-level workflows. The ISO examples reference compliance-quarterly-prefetch, compliance-monitoring-snapshot, compliance-evidence-sync, and compliance-vanta-final-check — these are planned system workflows. Until they ship, those workflow-typed actions degrade to manual checklists in the runtime UI.

Related