Publish a portable consumer-organization AI context and agent profile

[szmyty]

Outcome

Define and publish a portable Aether organization profile that lets downstream organizations consume the same versioned specifications, skills, agents, and repository-context behavior as Ego Hygiene while owning their own mission, architecture references, repository catalog, policy overlays, and private context.

The profile must prove that Aether's reusable AI layer is a platform capability rather than an Ego Hygiene-only instruction bundle.

Architecture

Aether released specs / skills / agents
        +
consumer organization profile
        +
organization architecture/context references
        +
repository-local context
        +
optional bounded Mindgarden context pack
        ↓
resolved agent profile
        ↓
provider projections / AGENTS guidance / task context

Aether owns portable agent semantics and projections. The consumer owns organization-specific intent and private context.

Current gap

Aether already has strong provenance, distribution, provider-projection, and repository-default work. The missing proof is an explicit external consumer organization contract demonstrating that organization-level AI behavior can be parameterized instead of copied and edited.

Required contract

Define a versioned consumer-organization AI profile with at least:

• stable organization ID;
• represented Hygiene Define the architecture materialization contract #42 organization-profile revision;
• pinned Aether distribution/catalog revision;
• organization architecture/context source references;
• repository-context resolution rules;
• selected skills/agents/specifications;
• organization-default and repository-specific overlay rules;
• provider compatibility/capability requirements;
• optional knowledge/context-pack inputs;
• visibility/sensitivity constraints;
• authority boundaries for read, plan, write, publish, and external actions;
• generated projection inventory and hashes;
• migration/rollback semantics.

The profile must not contain provider credentials, secrets, or private knowledge bodies.

Composition rules

• Canonical Aether artifacts remain provider neutral and versioned.
• Consumer organizations reference released artifacts; they do not fork Aether source to change organization wording.
• Organization-specific mission, vocabulary, architecture references, and policy remain consumer-owned inputs.
• Repository-local instructions may extend organization guidance only through documented seams.
• Private Mindgarden/context inputs remain runtime/local projections and never become part of public Aether packages.
• Missing or incompatible provider capabilities produce explicit diagnostics.
• Generated provider-specific files are disposable projections of the canonical profile and released Aether source.

Developer experience

A consumer should eventually be able to perform an explicit flow equivalent to:

validate organization AI profile
→ resolve selected Aether release
→ preview generated organization/repository projections
→ apply to a candidate tree
→ verify exact hashes and source revisions

The concrete CLI entry point may reuse existing Aether/Holon surfaces; this issue should not create a competing materializer if Holon is the correct apply owner.

Required proofs

1. Ego Hygiene organization profile.
2. Synthetic external organization with different vocabulary and repository classes.
3. Repository with an organization default plus bounded local override.
4. Provider projection with a missing capability.
5. Private Incompris canary consuming released Aether artifacts without committing private context upstream.

Acceptance criteria

• A versioned consumer-organization AI profile exists.
• The profile composes with egohygiene/hygiene#42 rather than redefining organization identity/policy.
• No canonical Aether spec/skill/agent requires the consumer owner to be egohygiene.
• Organization mission/context is consumer-owned data, not forked Aether prose.
• Repository-local overlays cannot silently override organization authority boundaries.
• Provider projections preserve source/profile revisions and hashes.
• Private/local context is referenced through bounded runtime inputs and cannot leak into public packages.
• Ego Hygiene remains a passing dogfood consumer.
• A synthetic non-Ego consumer passes clean validation/projection tests.
• A private Incompris canary can use the same release without copying Aether source.
• Holon and Realm integration boundaries are documented so generation/environment ownership remains clear.

Dependencies / related

• Define the portable organization-foundation contract and platform distribution lock hygiene#42
• Generalize Holon into a portable organization bootstrapper for downstream consumers holon#41
• Publish a repository-default skill bundle and generated AGENTS guidance #67 — repository-default skills and generated guidance
• Existing Aether artifact/provenance/distribution contracts
• Mindgarden context packs as an optional downstream input

Non-goals

• Making Aether the source of organization policy.
• Storing consumer secrets or private knowledge.
• Replacing Holon materialization or Realm environment setup.
• Requiring a specific model/provider.
• Publishing Incompris private context in Ego Hygiene repositories.