CORE's Author Follows CORE's Own Rules
The author of CORE, an AI-powered software development tool, realized they had been violating their own constitution by not writing a clear user requirements document for CORE itself. They describe the process of defining CORE's user requirements and integrating them into the project's governance.
Why it matters
This article highlights the importance of following one's own principles and rules, even for the tools and projects one creates. It demonstrates the value of clearly defining user requirements before implementation.
Key Points
- 1CORE has a rule that a constitution must be written before any code is written for a project
- 2The author realized they had not written a user requirements document for CORE, their own project
- 3After a conversation, the author was able to clearly articulate 8 user requirements for CORE
- 4The user requirements document was placed in the .intent/northstar/ directory, as it represents the concrete NorthStar for the project
Details
The author of CORE, an AI-powered software development tool, spent a Sunday not writing code, which they found to be their most productive day in months. They realized that while CORE has a strong constitution and governance system, the author had not actually written a clear user requirements document for CORE itself. CORE's rules state that a constitution must be established before any code is written, but the author had been quietly violating this rule. Through a philosophical conversation, the author was able to distill 8 concrete user requirements for CORE, covering aspects like universal input acceptance, comprehension before action, gap and contradiction reporting, and the primacy of the constitution over code. The author decided to place this user requirements document in the .intent/northstar/ directory, as it represents the concrete NorthStar for the CORE project.
No comments yet
Be the first to comment