PROFILE-Atoms
User/agent profile compositions for the Olympus broker.
The catalog of profile compositions — durable, signed declarations that establish a user's working identity in the
Olympus broker. Each profile composes role-packs (vocabulary), a policy stack (rules),
a governance stack (signing/audit), defaults (persona, theme, budget), availability sets (identities, channels),
knowledge sources, and default workflows.
Profile vs Situational Context
Profile and situational context are parallel inputs to the broker, not hierarchical layers.
A profile is who I am (durable). A situational context is what I'm doing (session-scoped).
Neither contains the other. See the design doc for the architectural model.
Profiles
Convergent Systems AI engineer working on the Olympus platform and the atoms catalog federation. Combines senior TypeScript/Python engineering with AI-system design, schema authoring, Cloudflare infrastructure, and the Conventional Commits + TDD discipline enforced by the governance constitution. References are placeholders until referenced catalogs are populated.
5 role-packs 5 policies 2 governance 2 identities 5 channels 4 knowledge 4 workflows
Authored by: convergent-systems-key
Non-fiction author working on long-form narrative with personal research substrate, voice consistency, and citation discipline. Illustrative profile from the v1.0.0 design — same logical schema as jmfamily-developer, completely different domain. References are placeholders until referenced catalogs are populated.
2 role-packs 3 policies 1 governance 1 identities 8 channels 4 knowledge 4 workflows
Authored by: personal-author-key
JM Family developer working on Python services with corporate engineering standards, SOX compliance, and TDD discipline. Illustrative profile from the v1.0.0 design — references to atoms in other catalogs are placeholders until those catalogs are populated.
4 role-packs 4 policies 2 governance 3 identities 5 channels 4 knowledge 3 workflows
Authored by: jmfamily-signing-key
For AI agents
Fetch /exports/catalog.json for the full machine-readable catalog.
Each profile is also reachable at /profiles/<namespace-slug>.json.
See how-to-use for the JSON shape and field semantics.