Inspect
Read the bootstrap contract, inspect the repository, and infer the most likely Sula profile.
read bootstrap
inspect repository
detect profile and project factsHow It Works
The actual usage flow should feel like this.
Report
Produce an adoption report before writing anything.
recommended profile
managed files: create / overwrite
scaffold files: create / preserve
blockers and warningsApprove
Wait for explicit user approval. No silent adoption.
User says:
批准接入
or
Approve adoption.Adopt
Apply the operating-system layer, validate the result, then explain what changed and how to use it.
render manifest and lockfile
apply managed files
preserve project-owned truth
run doctor --strict
report result and usageManaged Boundary
Sula should manage the operating system, not absorb project truth.
- Managed files can be synced later from Sula Core.
- Scaffold files are starters and stay owned by the project after first generation.
- Status, change history, release notes, and incident notes remain durable project memory.
- Approval is always required before adoption writes into a repository.
Current State
The site is in development, but the bootstrap contract is already usable.
- The public domain can host this exact static page set.
- The canonical bootstrap flow already exists in the Sula CLI.
- The source repository is not ready for direct public release from current history yet.
- The future public source should come from a clean Sula-only history.
What You Get
Normal usage already delivers concrete operational benefits.
Faster session startup
New agents stop behaving like empty-context contractors and start from explicit project rules.
Durable project memory
Rules, current status, decisions, releases, and incidents have fixed locations instead of chat-only history.
Safer shared upgrades
`sync --dry-run`, version locks, canaries, and strict doctor checks reduce blind rollout risk.