Use it. Report it. Improve it in the repository.
Use Casa, report failures, and contribute issues, playbooks, fixtures, or docs in the public repository. Zero dependencies. Golden fixtures follow the behavior.
Public repository / github.com/Capx-AI/casa
Real use becomes a reviewed catalog change.
MIT licensed. The working surface is public and inspectable.
Install Casa. Let actual work expose the gap.
Expected behavior, actual behavior, safe reproduction.
- node --test suite green
- Zero-dependency rule holds
- Golden fixtures updated with reasons
- Human review
The control plane should learn from more than one company.
Operating knowledge spans business models, regions, functions, and stages. The public repository is how that knowledge enters the commons without weakening the contracts. New work has to declare when it applies, what it depends on, what it produces, and how the engine can take it without changing unrelated company maps.
OPEN CORE / THESISContribution happens in the public repository. Run Casa on real work, name failures precisely, and add issues, playbooks, fixtures, or docs without weakening determinism, portability, or founder control.
How to participate
Use
Install Casa in the harness you already run. Notice where routing, context, artifacts, or gates fall short on a company you actually operate.
Report
Open an issue with the company shape, expected behavior, actual behavior, and any reproducible files you are authorized to share. Separate product defects from model taste.
Contribute
Issues, playbooks, fixtures, and docs are the main paths. Keep the scope narrow. One playbook, one invariant, or one documentation problem is easier to test and review.
Protect the contracts
Runtime stays at zero dependencies. If a change alters playbook selection, sequencing, or company maps, the golden fixtures and explanation change with it.
Code, playbooks, standards, and examples offer different ways to improve the layer.
Real usage is the strongest product review.
The best report names the company context, the recommendation Casa made, why it was wrong or incomplete, and what operating evidence should have changed it. Record the route that produced the issue. Share only artifacts you are authorized to publish. A small safe fixture is usually more useful than a full private brain.
- Name expected and actual behavior
- Attach a redacted fixture when you can
- Keep private company data private
Issues, playbooks, fixtures, and docs.
A playbook draft stays outside the catalog until it names applicability, prerequisites, a concrete deliverable, and a review bar. An engine change needs focused tests. Docs travel with behavior. Open an issue before a large implementation so scope can be challenged early.
- Playbooks declare when they apply
- Fixtures prove the intended behavior
- Docs change in the same contribution
The runtime stays at zero dependencies.
Casa's deterministic engine uses Node built-ins. Runtime additions are not accepted casually. The rule keeps the engine installable, portable, and consistent across harnesses. Development tooling has a separate bar. Do not move rules into prompt prose.
- Node 20+ and Node built-ins
- No runtime package additions by default
- Rules belong in code, not prompts
Behavior changes travel with golden fixtures.
If a change alters playbook selection, sequencing, or company maps, the relevant golden results and explanation change in the same contribution. New catalog entries must not distort unrelated companies. Reviewers should be able to observe the before and after.
- Golden maps change with routing behavior
- One reproducible result per change
- No hidden broadening of gates
The review bar
Evidence over volume
A precise reproduction beats a large thread.
Contribution happens in the repository
Issues and pull requests on github.com/Capx-AI/casa are the working surface. Public social channels are for conversation, not merges.
Company privacy first
Share only artifacts and state you are authorized to publish.
Examples stay examples
Do not present a demo, fixture, or unlabeled study as a live Capx listing or a public outcome.
Where to participate, what is public, and how contribution earns trust.
01Do I need to code to contribute?+
No. Playbooks, documentation, issue reproduction, review rubrics, and operating critique are valuable contributions.
02Where should I report a bug?+
Use the public Casa issue tracker. Support is public channels only, never DM.
03Can I add a dependency?+
The deterministic runtime keeps a zero-dependency rule. Development tooling has a separate bar. Runtime additions are not accepted casually.
04Do I need to update golden fixtures?+
Yes, when a change alters playbook selection, sequencing, or company maps. The golden results and explanation should change with the behavior.
05Where does contribution actually happen?+
In the public repository at github.com/Capx-AI/casa. Open an issue or a focused pull request there.
Open the repository.
Issues, playbooks, fixtures, and docs land there. That is where contribution happens.