Phase 09 · Change Proposals

After openlogos launch, every change to the system starts with a Delta proposal — a structured document that describes what changes, what is affected, and how the change propagates through the Spec Chain.

Why not just edit the code?

Direct code edits without updating the spec create drift. A month later, your API spec describes endpoints that no longer exist. Your test cases reference behavior that was silently changed. The Spec Chain loses its integrity.

Change proposals enforce the rule: spec first, code second.

Creating a change proposal

cd my-project && openlogos change <slug>

For example:

openlogos change add-oauth-login

This creates logos/changes/add-oauth-login/proposal.md with a template:

## Change: add-oauth-login

### What changes
...

### Affected artifacts
- [ ] requirements.md
- [ ] openapi.yaml
- [ ] schema.sql
- [ ] Test cases

### Impact analysis
...

The Change Skill

The Change Skill reads the proposal and the current Spec Chain to produce:

Updated requirements.md (new or modified acceptance criteria)
A diff of openapi.yaml (new endpoints or schema changes)
New or updated test cases
Code changes scoped to the affected modules

Merging a proposal

Once the AI has generated all artifacts:

openlogos merge <slug>

This applies the proposal's changes to the main artifacts and archives the proposal.

Back to overview

→ The Spec Chain overview