Skip to content

AIPHub and the roadmap

Implemented: local milestone

The Go CLI implements the six initial object types, deterministic CBOR, SHA-256 identities, local immutable storage, intent-aware snapshots, candidate history, file/text diff, graph verification, and reported/executed evidence.

The repository includes protocol tests, concurrency tests, and interoperability vectors. See the milestone acceptance record.

Experimental: transport foundation

The loopback-only HTTP development server implements object exchange and conditional publication of state and intent references. It supports private reads and writes, or public reads with authenticated writes.

This is not AIPHub. There are no hosted accounts, multi-user permissions, or remote synchronization CLI commands yet.

Next core work

  1. Workspace filtering is implemented: a root .aipignore keeps dependency folders, generated output, and local environment files out of observation. Already recorded artifacts remain in immutable history.
  2. Release provenance. Add signed release manifests and broader native platform testing. Binary previews and checksum-verifying installation are available now; signatures are not.
  3. Synchronization CLI. Transfer missing objects and verify the graph between independent repositories before adding hosted accounts.
  4. Hosted repository access. Establish private-by-default storage and per-repository authorization before publishing AIPHub’s first repository UI.

Agent onboarding now includes aip agent setup, root instructions, and a local .aip/AGENTS.md guide. These instructions help agents follow the workflow but do not automatically enforce project constraints.

Planned: AIPHub

AIPHub will provide hosted collaboration around AIP repositories:

  • Public and private repositories with repository-level access control.
  • Browsable intents, candidate states, decisions, and evidence.
  • Remote object storage and transfer of missing objects.
  • Candidate comparison, agent activity, and human review.
  • Later, isolated evaluation and previews with explicit execution limits.

AIP remains usable locally and independently of AIPHub. The protocol and Go reference implementation are Apache-2.0 licensed. Hosting and managed execution are potential paid services; pricing and availability are not announced.

Deliberately deferred

Git adapters, semantic AST diffing, automatic synthesis, model integrations, packfiles, and language SDKs are outside the first local milestone.