Community contributions

Contribute hooks, findings, and atoms

The aiConstitution system is meant to be contributed to. Each contribution type has its own upstream repo and issue template.

Hooks & findings — this repo

The ai binary itself, the Python hook library, and the methodology spec all live at convergent-systems-co/aiConstitution . File:

• Hook contribution — a new hook (or improvement to an existing one), typically grown from a logged finding. Filed automatically by ai hooks share <name>.
• Finding — a recurring pattern or behavior worth tracking, not yet a hook.
• Epic / Feature / Story / Task — the canonical work-decomposition hierarchy.

Atoms — sibling repos

• Persona atoms: persona-atoms.com. Repo: convergent-systems-co/persona-atoms. Submit via ai persona share <name> (agentic) or with --domain (reviewer).
• Profile atoms: profile-atoms.com. Repo: convergent-systems-co/profile-atoms. Submit via ai profile share <name>.
• Skill atoms: skill-atoms.com. Repo: convergent-systems-co/skill-atoms. Submit via ai skills share <name>.
• Brand atoms: brand-atoms.com. Repo: convergent-systems-co/branding-library.

What about security?

Do not open a public issue for a security finding. Email security@convergent-systems.co instead. The contact link is also wired into the repo's .github/ISSUE_TEMPLATE/config.yml so the in-repo issue picker surfaces it directly.