Three conceptual operating modes.

Current availability, operational boundaries, and licensing intent across development environments.

Open FoundationActive Local Reference

Local / Community

Intended Role

Individual developers, open-source maintainers, and local CLI workflows.

Current Availability

Available now in repository workspaces and local terminal execution.

Data Boundary

100% on-device. Source code, AST indexes, and .trace files remain strictly local.

Licensing Intent

Planned free core for local artifact generation and repository governance.

Under ValidationValidation in Progress

Team Cloud

Intended Role

Engineering teams coordinating multi-branch changes, PR briefs, and daily digests.

Current Availability

Early preview validation. No checkout, credit card capture, or paid tier is live.

Data Boundary

Ephemeral projection. Synchronizes signed summaries; zero raw source code stored.

Licensing Intent

Pricing structure will be defined strictly by verified team coordination value.

Design PartnershipPartner Validation

Enterprise / Private

Intended Role

Organizations requiring self-hosted or network-isolated runtimes, VPC isolation, and custom security policies.

Current Availability

Requirements and operational constraints defined with pilot design partners.

Data Boundary

Self-hosted control plane or customer-managed cloud isolation boundaries.

Licensing Intent

Formal enterprise packaging and support terms will be announced after pilot audit.

Commercial commitments.

Core principles governing software value, artifact freedom, and future pricing.

Portability Invariant

Zero commercial gating on the `.trace` format

The .trace artifact standard (RFC-001) is open, transparent, and portable. You will never need a paid subscription to inspect, parse, or commit your own project memory.

Product Discipline

Evidence before monetization

We are focused on eliminating noise and proving bounded AST change intelligence before introducing paid commercial tiers. No checkout flows exist in this build.

Zero Lock-in

No proprietary repository lock-in

Because Git remains the sole authority and artifacts are stored in human-readable Markdown, your project intelligence survives regardless of subscription status.

Start with the early validation build

Experience change intelligence on live repositories, evaluate multi-branch conflict detection, or review the open specification without financial commitment.