Craik Documentation
Craik's v0.1.0 documentation is organized for agents and humans entering a project.
Craik v0.1.0 is a governed runtime substrate, not a broad autonomous agent release. It supports typed case files, policy envelopes, receipts, prompt compilation, fixture and live-shaped provider transports, provider-backed loop execution, typed credential profiles, OIDC operator identity, handoffs, work graphs, and memory proposals. Live model calls are explicitly enabled and credentialed through auth profiles or credential pools; unbounded tool execution, unattended edits, and production multi-agent orchestration remain outside the current MVP surface.
Start Here
- Installation
- Quickstart
- Stigmem Documentation Demo
- CLI Reference
- Limitations
- Robust MVP Roadmap
- Architecture Decision Records
Concepts
- Project Model
- Case Files
- Governance
- Handoffs
- Receipts
- Memory And Stigmem
- Single-Agent Execution Loop
- Work Graph
- Intent Locks
Guides
- Configuring Craik Home
- Setup Wizard
- Doctor Diagnostics
- Authentication and Credentials
- Updating Craik
- Gateway Troubleshooting
- Provider Routing And Sandboxes
- Project Registry
- Using Case Files
- Agent Onboarding
- Writing Handoffs
- Managing Instructions
- Memory Proposals
- Contradiction Inbox
- Connecting Stigmem
- MCP Ecosystem Compatibility
- Running Policy Tests
- Runner Preview Workflows
- Single-Agent Fixture Loop
- Learning Loops
- Companion App Security
- Community Skills
- Community Plugins
- Translated Documentation Strategy
- Development Checks
Reference
- CLI
- Config
- Operator Surface
- Work Graph Explorer
- Handoff Viewer
- Receipt Viewer
- Contradiction Inbox View
- Evidence And Assumption View
- Delegation Queue View
- Budget And Quota View
- Instruction Distillation View
- Quality Gate View
- Memory Impact Preview View
- Memory Review Nudges
- Preference Facts
- Known Traps View
- Run Delta View
- Gateway Daemon Mode
- Channel Adapter Contract
- Messaging Channel Adapter
- Channel Identity Pairing
- Channel Allowlists
- Channel Policy Envelopes
- Webhook Ingress
- Scheduled Task Creation
- Scheduled Automations
- Gateway Receipts
- Model Providers
- Provider Certification
- Provider Switching
- Provider Failover
- MCP Export Boundary
- MCP Client
- Sandbox Backends
- Local Process Backend
- Remote Shell Backend
- Environment Receipts
- Browser Tool Boundary
- Docker Sandbox Backend
- Schemas
- Agent Roles
- Adapter Packages
- Worker Results
- Structured Debates
- Role Dispatch
- Agent Mailbox
- Scope-Change Protocol
- Intent-Lock Coordination
- Identity Isolation
- Cross-Agent Review
- Context Debt
- Tool Attestations And Freshness
- Known Traps And Negative Knowledge
- Scratchpad And Unknowns
- Context Requests And Exit Discipline
- Skill Packages
- Skill Registries
- Skill Invocation Contexts
- Skill Telemetry
- Skill Proposals
- Skill Replay
- Skill Promotion Gates
- Learning Receipts
- Training Trajectory Exports
- Skill Rollbacks
- Voice Input And Output Posture
- Multimodal Artifact References
- Speech-To-Text Adapter Contract
- Text-To-Speech Adapter Contract
- Desktop Companion App Decision
- Mobile Companion App Decision
- Live Visual Workspace Decision
- Work Graph Visual Workspace Bridge
- Accessibility Requirements
- Adjacent-Tool Migration Assessment
- Multi-Agent Workflow Migration Assessment
- Import Dry-Run Reports
- Migration Maps
- Secret Migration Policy
- Adjacent Runtime Bridge
- Multi-Agent Workflow Bridge
- Locale I18n Framework
- Plugin Descriptors
- Plugin Probation
- Plugin Receipts
- Plugin Capability Grants
- Reference Integrations
- Human Delegation
- Instruction Sources
- Distilled Instructions
- Instruction Approval
- Instruction Distillation Workflow
- Recovery Mode
- Runtime Critics And Red Team
- Quality Scores
- Runner Adapter Contract
- Runner Step Contracts
- Codex Runner Adapter
- Claude Runner Adapter
- Gemini Runner Adapter
- Runner Metadata
- Run State
- Prompt Compiler
- Policy Profiles
- Policy Tests
- Memory Backends
- Stigmem Compatibility
- Local State
- Local Store
- Redaction
- Secrets
Public Boundary
Public docs must describe product behavior and supported workflows without internal-only planning labels, private task names, local filesystem paths, or credentials. ADRs and configured immutable docs are evidence, not normal edit targets.