A stateful human–agent operating system for turning evolving intent into governed action, durable knowledge, and an inspectable shared world.

Quirk connects humans, agents, repositories, tools, evidence, and decisions through one persistent operating loop:

async preparation
→ real-time session
→ async execution
→ real-time review
→ persistent world update

The conversation is not the system. The agent is not the system. The repository is not the system.

The governed, versioned state connecting them is the system.

• quirk-os — the implemented Quirk kernel, currently awaiting its repository-name cutover
• quirk-feed — knowledge-feed and discovery surface
• quirk-generator — multi-model visual-generation instrument
• .github — public governance, semantic authority, and reusable organization workflows

• Git-canonical, runtime-projected. Canonical definitions are versioned and reviewed; databases and interfaces are projections.
• Human authority over consequential change. Agents prepare, propose, execute bounded work, and return evidence.
• Containment before capability. Every agent and automation receives explicit objectives, permissions, limits, and shutdown authority.
• Second consumer before extraction. Shared modules become packages or repositories only when real reuse, security, scaling, or release boundaries justify the split.
• Every decision updates the world. Accepted work changes canonical state, not merely a conversation or task status.

The organization’s repository classes, lifecycle rules, creation gate, extraction criteria, and management system are defined in docs/REPOSITORY_STRATEGY.md.

See CONTRIBUTING, our Code of Conduct, and the security policy.