Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hopsule.com/llms.txt

Use this file to discover all available pages before exploring further.

A Decision is a structured statement of what the team agreed for the project. Decisions are the durable rules assistants and the IDE should respect. Enforcement in Git stays advisory: warnings and context, not automatic merge blocks from Hopsule. Unlike docs that rot in a wiki, decisions are first-class data with lifecycle and history.

​
Human approval

Decisions follow a lifecycle (Draft to Pending to Accepted to Deprecated). AI can propose wording; people with the right permissions move states. Humans review and approve promotions in the workflow.

​
Technical authority (how the product stores rules)

For integrations and AI behavior, Hopsule treats accepted decisions as immutable records in its hosted backend: decision-api is the system of record for that stored data. Editors, MCP, and CLI are consumers of those records. They reflect accepted decisions in warnings and retrieved context; they do not rewrite an accepted decision in place. No external AI overrides an accepted decision as stored in Hopsule.

​
Decision lifecycle

1

DRAFT

Work in progress. Fully mutable; AI can suggest improvements to the statement.
2

PENDING

Submitted for review. The system can run conflict analysis against existing rules.
3

ACCEPTED

Immutable for the statement as approved. Becomes the basis for advisory checks and grounded AI context, with a clear audit trail.
4

DEPRECATED

When architecture evolves, older decisions are deprecated (superseded), not deleted, so history stays intact.
Once a decision is ACCEPTED, its text is not edited in place. Immutability keeps trust in your organizational memory.