Atomic Concepts

Table of contents
  1. Atomic Concepts
    1. All atoms
    2. Lens — regulated
    3. Lens — security
    4. Lens — by domain
    5. Lens — by standard
    6. Lens — uncomposed

The freestanding semantic units of Grace Commons — each fully specifiable without naming another atom. Atoms are stored flat (atoms/<name>.md); their classification is not a folder but a set of lenses over the Intent Graph. Overlays (regulated · security · standards) are read off the composition graph and report usage, not essence — a standard shows as HIPAA via audit-trail, an uncomposed atom as composed by: (none yet), never a bare boolean. Domain is the one intrinsic axis: an optional, EOS-gated tag, default absent. The design and its rationale are in the taxonomy note.

25 compositions (22 regulated) · 27 atoms · 63 composition→atom edges. Generated from tools/taxonomy/reverse_index.py; regenerate with python3 tools/taxonomy/generate_views.py .

All atoms

Atom Domain Regulated Security Composed by
Actor Identity — yes (5) yes actor-suspension, attributed-permissions-admin, audit-trail, authenticated-actor, reserve-from-pool
Approval Step — yes (2) — execute-gated-workflow, multi-party-approval
Assignment — yes (2) — execute-gated-workflow, multi-party-approval, shared-todo
Capability — yes (2) yes capability-backed-sharing, privileged-access-provisioning
Capacity Constraint Enforcement — yes (1) — reserve-from-pool
Clinical Observation — — — (none yet)
Consent — yes (2) — propagate-consent-revocation-downstream, resolve-a-persons-data-rights
Credential — yes (4) yes authenticated-actor, external-onboarding, login, privileged-access-provisioning
Duplicate Prevention — yes (2) — idempotent-reservation, reserve-from-pool
Event Log — yes (3) — audit-trail, compensable-workflow, preference-aware-notification-fanout, reserve-from-pool, undo-history
Invitation — yes (1) yes external-onboarding
Legal Hold — yes (1) — defensible-retention
Medication Order healthcare — — (none yet)
Message Preference — yes (1) — preference-aware-notification-fanout
Notification — yes (2) — notification-fanout, preference-aware-notification-fanout
Party Identity — yes (2) yes customer-onboarding, external-onboarding
Permissions — yes (7) yes actor-suspension, attributed-permissions-admin, execute-gated-workflow, multi-party-approval, privileged-access-provisioning, propagate-consent-revocation-downstream, session-gated-authorization, shared-todo
Personal Todo — — — shared-todo, undo-history
Provenance — yes (1) — chain-of-custody
Provisional Commitment — yes (2) — idempotent-reservation, reserve-from-pool
Retention Window — yes (4) — audit-trail, customer-onboarding, defensible-retention, propagate-consent-revocation-downstream
Selective Disclosure — yes (3) — capability-backed-sharing, immutable-transaction-ledger, resolve-a-persons-data-rights
Session — yes (4) yes actor-suspension, login, privileged-access-provisioning, session-gated-authorization
Soft Delete — yes (1) — forensic-recovery
State Machine — yes (1) — compensable-workflow, execute-gated-workflow
Subscription — yes (2) — notification-fanout, preference-aware-notification-fanout
Tamper Evidence — yes (1) — audit-trail

Lens — regulated

Atoms that a regulated composition (one carrying a ## Generation acceptance section) composes. Derived, attributed per composer.

  • Actor Identity — via actor-suspension, attributed-permissions-admin, audit-trail, authenticated-actor, reserve-from-pool
  • Approval Step — via execute-gated-workflow, multi-party-approval
  • Assignment — via execute-gated-workflow, multi-party-approval
  • Capability — via capability-backed-sharing, privileged-access-provisioning
  • Capacity Constraint Enforcement — via reserve-from-pool
  • Consent — via propagate-consent-revocation-downstream, resolve-a-persons-data-rights
  • Credential — via authenticated-actor, external-onboarding, login, privileged-access-provisioning
  • Duplicate Prevention — via idempotent-reservation, reserve-from-pool
  • Event Log — via audit-trail, preference-aware-notification-fanout, reserve-from-pool
  • Invitation — via external-onboarding
  • Legal Hold — via defensible-retention
  • Message Preference — via preference-aware-notification-fanout
  • Notification — via notification-fanout, preference-aware-notification-fanout
  • Party Identity — via customer-onboarding, external-onboarding
  • Permissions — via actor-suspension, attributed-permissions-admin, execute-gated-workflow, multi-party-approval, privileged-access-provisioning, propagate-consent-revocation-downstream, session-gated-authorization
  • Provenance — via chain-of-custody
  • Provisional Commitment — via idempotent-reservation, reserve-from-pool
  • Retention Window — via audit-trail, customer-onboarding, defensible-retention, propagate-consent-revocation-downstream
  • Selective Disclosure — via capability-backed-sharing, immutable-transaction-ledger, resolve-a-persons-data-rights
  • Session — via actor-suspension, login, privileged-access-provisioning, session-gated-authorization
  • Soft Delete — via forensic-recovery
  • State Machine — via execute-gated-workflow
  • Subscription — via notification-fanout, preference-aware-notification-fanout
  • Tamper Evidence — via audit-trail

Lens — security

An overlay, not a domain: an atom carries it iff it derives an identity / access / crypto-family standard (NIST 800-63/53/207, OWASP ASVS, SCIM, FIPS 180-4). Cross-cutting and multi-valued — an atom can hold it alongside any domain.

Lens — by domain

The one intrinsic axis. A domain earns a tag only when stripping it fails to leave a freestanding, domain-neutral primitive (the EOS test); default absent. The system is correct with zero domain tags — domain is additive, never load-bearing.

Lens — by standard

The union of standards each atom’s composers carry, attributed per composer in the atom’s own page.

Lens — uncomposed

Atoms no composition yet composes. The overlays say nothing about them — an honest gap, not a claim of non-regulation.

For structured assemblies of atoms, see Compositions.

Table of contents

↑