Develop Colossus¶

This lane is for contributors changing Colossus itself. Product installation and normal operation stay in Get started and Administer and secure.

• Contributing explains repository conventions and change ownership.
• Source setup and test tiers provides a reproducible development loop.
• Tiered CI/CD explains the cost-bounded PR, pre-merge, and release gates.
• Core release operations covers registry bootstrap, stable CLI/SDK publication, and partial-release recovery.
• Architecture overview defines dependency direction.
• Rust crate structure keeps crate roots readable and behavior in responsibility-focused modules.
• Rust engineering practices defines repository-specific ownership, API, async, error, and review guidance.
• Test strategy and crate audit maps test levels and retained evidence for every workspace crate.
• Feature ownership inventory locates current implementations, documentation, and acceptance evidence.
• Architecture decisions retain the context behind durable boundary and migration choices.
• Runtime and ports maps application responsibilities.
• Public API and application SDKs defines the gRPC, SDK, and Tauri integration boundary.
• State and recovery explains canonical state and replay.
• Security architecture defines the non-bypassable effect path.
• Extension and presentation architecture covers dynamic capability and UI boundaries.
• Documentation authoring defines the public information contract.

Read the architecture and security pages before changing boundaries. Keep interfaces thin, the domain dependency-free, and behavior changes covered by tests.