Cullinan Documentation

Current version: 0.93a13. The shortest public startup path is @application + @configure(...) + main(); the semantic learning path starts from top-level cullinan plus the business-facing cullinan.web / cullinan.core vocabulary: begin with business decorators and business methods first, then enter advanced application/runtime details only when the application really needs them.

Default learning path

1. Application Build
2. Framework Semantics
3. Engineering Practices
4. API Reference

This path is the default for most developers using Cullinan to build business applications. It intentionally keeps advanced runtime internals and version migration notes outside the first-read path.

Documentation map

1. Application Build

Use this section to bootstrap a new application with the recommended public API.

• Getting Started
• Examples
• Build & Run

2. Framework Semantics

Use this section to understand how Cullinan thinks and why it discourages explicit app-centric wiring.

• Framework Semantics
• Architecture

3. Engineering Practices

Use this section for task-oriented guides.

• Dependency Injection Guide
• Web Runtime Guide
• Parameter System Guide
• Testing & Verification

4. API Reference

Use this section for symbol lookup and stable API surface review.

• API Reference Overview
• Module references stay in this section for lookup only.
• Prefer the overview first, then read controller, service, or core references as needed.
• Advanced application/runtime surfaces remain outside the default first-read path.

5. Internals & Extensions

Use this section only when you intentionally need advanced runtime or extension knowledge.

• Application Runtime Model
• Extension Development Guide
• Quick Start Extensions

6. Migration & Version Notes

Use this section when upgrading or reconciling old code with newer semantics.

• Runtime Consolidation
• Migration Guide
• Migration Guide v2
• Import Migration 0.90

For source code and release history, visit the GitHub repository.