Shared elements and approved reuse
This register records conceptual reuse, not proof that one shared software component exists.
| Shared element | Kind | Created-for context | Supported capabilities | Reuse status | Notes |
|---|---|---|---|---|---|
| Stable source reference | data/information MLE | governed retention | derivation, retrieval, consolidation, term detection | conceptually approved | Representation remains implementation-specific. |
| Governed proposal | domain/interaction MLE | proposal decisions | term promotion, assisted-label vocabulary, standing rules | approved by capability relationship | Uses decide-governed-proposal; does not duplicate its contract. |
| Glossary identity and aliases | data/information MLE | personal glossary | candidate detection, retrieval, Cotton application | conceptually approved | External standard mappings remain secondary. |
| Provenance record | data/operations MLE | cross-cutting | all evidence-producing capabilities | conceptually approved | Minimum fields depend on the governed object and risk. |
| Lifecycle history | data/operations MLE | proposals and context links | glossary, labels, contextual classification, rule governance | conceptually approved | History preservation does not imply one universal table. |
| Context receipt | data/operations MLE | governed retrieval | later context compilation and disclosure capabilities | conceptually approved | Retention period remains unresolved. |
| Version/revision relation | data/information MLE | knowledge notes | glossary terms, profile assertions, governed system definitions | conceptually approved | Exact storage representation is not fixed. |
| Evidence link | data/information MLE | profile assertions | proposals, term candidates, consolidations, derived content | conceptually approved | Evidence does not by itself grant authority. |
| Execution run record | data/operations MLE | governed action invocation | background operations, workflows, results, standing-rule applications | conceptually approved | Each domain capability defines its own success semantics. |
| Action declaration | API/system MLE | governed action invocation | execution policy, skills, workflows, capability discovery | conceptually approved | A declaration is not proof of availability. |
| Source-to-derived execution link | data/information MLE | plan activation | projects, routines, results, reusable structures derived from completed work | conceptually approved | Derivation preserves the source object and activation decision. |
| Canonical work-state record | data/operations MLE | projects and tasks | routine runs, workflows, background operations, Work Starters | conceptually approved | Communication wrappers may project state but are not canonical state stores. |
| Trigger and recurrence definition | data/operations MLE | reminders | routines, workflow triggers, scheduled operations | candidate for reuse | Each consuming capability retains its own authority and outcome semantics. |
| Work-source context link | data/information MLE | Work Starters | tasks, projects, plans, routine runs, results | conceptually approved | A projection never replaces the canonical source object. |
| Immutable execution snapshot | data/operations MLE | workflow runs | routine runs, background operations, governed actions | conceptually approved | Snapshot scope is capability- and risk-specific. |
| Result provenance bundle | data/information MLE | execution results | projects, routine runs, workflow runs, completed-work updates, History | conceptually approved | Result qualification remains distinct from generic retention. |
| Canonical event envelope | data/information MLE | event recording | work completion, processing, updates, History, governance, imports | conceptually approved | Event-family requirements extend the minimal stable envelope. |
| Owner-attention state | data/operations MLE | owner attention items | reminders, decisions, incidents, workflow outcomes, completed work | conceptually approved | Read/pin/dismiss state does not alter source truth. |
| History period link | data/information MLE | History aggregation | daily compilation, higher summaries, time-first retrieval | conceptually approved | Parent and child periods retain drill-down provenance. |
| Source definition | data/information MLE | connected-source registration | import sessions, mapping, event creation, promotion, export | conceptually approved | Source identity persists independently from sessions and jobs. |
| Versioned batch manifest | data/operations MLE | ingestion screening | readiness assessment, owner authorization, execution, parity proof | conceptually approved | Any material manifest change invalidates stale gate evidence. |
| Ingestion gate receipt | data/governance MLE | ingestion screening | readiness and authorization | conceptually approved | Each receipt records its limited authority and cannot substitute for another gate. |
| Event-type definition | data/system MLE | event registry governance | event recording, projection maintenance, lifecycle validation | conceptually approved | Registry acceptance does not record an occurrence. |
| Operational run evidence | data/operations MLE | run execution | inspection, incident review, retry decisions, completed-work publication | conceptually approved | Missing evidence remains visible rather than inferred. |
| Portability manifest | data/interoperability MLE | portable package composition | Core-export and source-composed package creation, validation, restore, parity, cutover | conceptually approved | Records package class, scope, versions, counts, integrity, exclusions, provenance, and compatibility notes. |
| Integrity digest set | data/verification MLE | portable bundle composition | package validation, backup verification, restored-state parity | conceptually approved | Algorithm and coverage remain explicit. |
| Import/operationalization report | data/operations MLE | bundle restore | parity validation, connector reauthorization, cutover review | conceptually approved | Separates accepted, rejected, quarantined, and unresolved content. |
| Recovery evidence receipt | data/verification MLE | restored-state parity validation | backup status, incident recovery, owner assurance | conceptually approved | A receipt identifies tested scope and does not imply broader recovery. |
| Canonical-side declaration | data/governance MLE | Core cutover | shadow operation, rollback, conflict reconciliation, source decommissioning | conceptually approved | Exactly one canonical side is named for each governed flow. |
| Transition delta ledger | data/operations MLE | Core cutover | rollback, parity validation, final reconciliation | conceptually approved | Tracks writes and acceptance across the transition boundary. |
| Erasure disposition record | data/governance MLE | data erasure | request status, derived cleanup, retention exception, source decommissioning | conceptually approved | Distinguishes hidden, deleted, expired, retained, and cryptographically inaccessible states. |
| Connector definition | data/interoperability MLE | source registration | portability export, restore, destination reauthorization | conceptually approved | Definition excludes live credentials and does not grant authority. |
| Capture receipt | data/operations MLE | governed content capture | pending reconciliation, intake status, duplicate detection, owner feedback | conceptually approved | Submission receipt does not by itself prove canonical acceptance. |
| Pending-capture reconciliation evidence | data/verification MLE | pending capture reconciliation | retry, conflict handling, accepted-content cleanup, owner attention | conceptually approved | Records acceptance or another explicit disposition before temporary data is released. |
| Onboarding journey record | data/operations MLE | guided onboarding | contact verification, identity setup, environment preparation, first-entry authorization | conceptually approved | Coordinates progress without replacing each capability's evidence. |
| Personal AI identity definition | data/system MLE | personal AI identity | onboarding, communication surfaces, sender presentation, portability | conceptually approved | Contains presentation identity, not separate memory or authority. |
| Personal AI interaction preference set | data/governance MLE | interaction preferences | onboarding, conversational presentation, proposal cadence, evidence display | conceptually approved | Does not replace execution policy or request-scoped instruction. |
| Environment preparation report | data/operations MLE | initial environment preparation | first-entry review, later personalization, onboarding export | conceptually approved | Distinguishes explicit, defaulted, inferred, omitted, and failed values. |
| First-entry authorization record | data/security MLE | first-entry authorization | journey completion, entry audit, credential replacement and recovery | conceptually approved | Stores protected credential references and bounded lifecycle evidence, not reusable secrets. |
| Owner Role definition | data/context MLE | Role maintenance | active context, contextual classification, retrieval, scheduling, outward intent | conceptually approved | Role type and Role instance remain distinguishable. |
| Owner operating Mode definition | data/context MLE | Mode maintenance | active context, contextual classification, retrieval, scheduling | conceptually approved | Operating Mode remains distinct from task working mode. |
| Active-context snapshot | data/context MLE | active personal context | capture inheritance, filtering, retrieval, scheduling, owner interfaces | conceptually approved | Carries source, timing, scope, and supersession evidence. |
| Role outward-intent declaration | data/governance MLE | outward-intent configuration | representation preparation, later sharing and publication review | conceptually approved | Does not itself expose content or grant access. |
| Source-to-outward-representation link | data/provenance MLE | outward representation preparation | revision, withdrawal, redaction review, publication evidence | conceptually approved | Preserves the unchanged private source and transformation history. |
| Pattern evidence bundle | data/information MLE | observed-pattern detection | lifecycle evaluation, proposal rationale, inspection, profile provenance | conceptually approved | Evidence remains source-linked and does not itself assert a pattern or profile fact. |
| Pattern lifecycle snapshot | data/verification MLE | observed-pattern lifecycle evaluation | trend inspection, proposal eligibility, decay review, audit | conceptually approved | Records evaluated status and measures without replacing source evidence. |
| Direction relationship | data/information MLE | goal and objective maintenance | targets, plans, projects, tasks, Work Starters, reviews | conceptually approved | Links preserve independent identities and do not require one universal hierarchy. |
| Success-condition definition | data/information MLE | target maintenance | goals, objectives, projects, review, progress projection | conceptually approved | The condition does not prove attainment. |
| Measurement definition | data/information MLE | measurement-definition maintenance | metric observations, target evaluation, summaries, patterns | conceptually approved | Definition versions remain distinguishable when comparability changes. |
| Metric observation | data/evidence MLE | metric-observation recording | progress review, aggregation, target evaluation, pattern analysis, profile evidence | conceptually approved | One observation remains evidence rather than an aggregate or assertion. |
| Outward exposure state | data/governance MLE | controlled sharing and publication | access enforcement, discoverability, rights, withdrawal, inspection | conceptually approved | Visibility is one axis and does not collapse the other controls. |
| Audience grant | data/authorization MLE | outward access-policy maintenance | controlled sharing, request evaluation, collaboration, delivery, revocation | conceptually approved | Audience identity and grant scope remain distinct from share delivery, access decisions, and content rights. |
| Discoverability declaration | data/governance MLE | outward discoverability | publication, indexes, listings, sitemaps, withdrawal verification | conceptually approved | Declared intent does not guarantee third-party propagation. |
| Outward usage-rights declaration | data/governance MLE | outward usage-rights governance | publication, sharing, machine-readable policy, compliance review | conceptually approved | Declared rights and proven external enforcement remain distinguishable. |
| Publication revision | data/provenance MLE | governed publication | republishing, withdrawal, audit, public History, source reconciliation | conceptually approved | Each outward revision retains source and policy context. |
| Review scope manifest | data/operations MLE | structured review | periodic review, event-triggered review, stale-item review, objective and project review | conceptually approved | Records included inputs, exclusions, questions, period, and reviewer authority. |
| Carry-forward reference | data/information MLE | structured review | tasks, Work Starters, attention items, goals, projects, later reviews | conceptually approved | Preserves the unresolved object's identity rather than copying it into a new truth record. |
| Person identity reference | data/information MLE | human contact profiles | contact points, relationship context, with-whom context, profile evidence, Circle | conceptually approved | A stable identity reference does not assert a relationship, contact method, or access grant. |
| Contact-point record | data/information MLE | contact-point maintenance | verification, communication preparation, account recovery, onboarding | conceptually approved | Value, normalized comparison form, label, provenance, and status remain distinct. |
| Contact-point verification evidence | data/security MLE | contact-point control verification | onboarding verification, contact presentation, account and recovery profiles | candidate for reuse | Method and assurance must remain visible; verification does not establish general identity or authority. |
| Relationship-context record | data/knowledge MLE | relationship-context maintenance | retrieval, Circle scope, sharing review, active context, contact views | conceptually approved | Relationship meaning and participant identities remain separately governed. |
| Relationship-origin evidence | data/provenance MLE | relationship-context maintenance | contact profile, relationship review, shared-history reconstruction | candidate for reuse | Origin story or introduction context is supporting evidence, not a standalone capability. |
| Canonical agent-definition version | data/system MLE | agent-definition maintenance | runtime synchronization, capability discovery, permission review, portability | conceptually approved | Runtime-local files and prompts identify the source version but do not replace it. |
| Runtime-target binding | data/operations MLE | agent-definition synchronization | deployment, rollback, health inspection, agent profile surfaces | conceptually approved | Records expected and effective versions plus intentional differences. |
| Agent runtime-role assignment | data/operations MLE | runtime-role assignment | orchestration, delegation, handoff, responsibility tracking | conceptually approved | Role scope and duration do not grant undeclared permissions. |
| Outward-identity selection | data/governance MLE | outward-identity selection | representative conversation, messaging, publication, external action audit | conceptually approved | Records represented party, agent identity, disclosure, scope, authority, and expiry. |
| Representative knowledge scope | data/authorization MLE | owner-representative conversation | retrieval, response generation, inspection, revocation | conceptually approved | Explicit outward allocation excludes private Core material by default. |
| Collaboration channel identity | data/collaboration MLE | collaboration-channel maintenance | discussion threads, participant views, notifications, harness interoperability | conceptually approved | Stable identity survives renaming and archival; the channel is not a work or knowledge record. |
| Work-linked thread reference | data/information MLE | discussion-thread maintenance | background operations, tasks, projects, results, reviews, owner attention | conceptually approved | Links one focused discussion to a canonical subject without copying its state. |
| Attributed communication envelope | data/security MLE | collaboration-message recording | chat, Circle, agent bridges, request queues, notifications | conceptually approved | Preserves actor, context, references, trust and trigger controls; natural-language content is not authority. |
| Execution-workspace manifest | data/operations MLE | execution-workspace management | background operations, workflow runs, agent coordination, result promotion, recovery | conceptually approved | Distinguishes inputs, temporary state, produced artifacts, dispositions and cleanup evidence. |
| Conversation-history membership | data/information MLE | personal conversation history | messages, imports, retrieval, consolidation, context classification, source-aware browsing | conceptually approved | Records logical inclusion and order without requiring one physical timeline table. |
| Owner access-path record | data/security/operations MLE | owner access-path maintenance | interface routing, availability inspection, recovery, break-glass review | candidate for reuse | Records role, endpoint identity, assurance, supported operations, health and verification without storing secrets. |
| Device-cache entry | data/operations MLE | authorized device-cache maintenance | local-copy access, shared device support, reconnect handling, cache inspection | conceptually approved | Binds owner/Core identity, logical reference, non-canonical state, and any validation evidence required by the declared implementation profile. |
| Offline-retention selection | data/authorization MLE | selected offline-content maintenance | offline browsing, device status, revocation, reconciliation | conceptually approved | Identifies the retained scope, device, authorization window, allowed offline operations and current state. |
| Reading-queue membership | data/experience MLE | personal reading-queue management | Reader views, reminders, progress summaries, contextual ordering | conceptually approved | References retained content and keeps unread/read/saved/archive state separate from source lifecycle. |
| Operation cost estimate | data/governance MLE | resource-cost estimation | proposals, execution policy, budget reservation, scope selection, owner attention | conceptually approved | Records scope, unit, range/class, assumptions, method, uncertainty and validity without granting authority. |
| Operation resource reservation | data/operations MLE | resource-budget reservation | background operations, workflows, imports, generation, reconciliation | conceptually approved | Binds an expiring internal allowance to one operation and authority basis. |
| Resource reconciliation record | data/evidence MLE | resource-usage reconciliation | usage History, future estimation, budget review, partial-completion decisions | conceptually approved | Preserves estimate, reservation, actual observations, variance, completed scope and remaining scope. |
| Source-discovery candidate record | data/evidence MLE | candidate source discovery | source review, permission decision, source registration, cost estimation | conceptually approved | Preserves submitted subject, candidate location/type, confidence, access/security notes, expected frequency, likely cost, actor and time. |
| Implementation-documentation reference | data/information MLE | owner implementation documentation | agent definitions, machine profiles, configuration review, recovery, onboarding | candidate for reuse | Links human-readable explanation to the governed object or configuration without copying secrets or silently becoming source truth. |
| Knowledge-integrity finding | data/evidence MLE | knowledge-layer integrity assessment | structured review, owner attention, note revision, concept lifecycle, access review, index rebuild | conceptually approved | Records checked scope, profile/rule, evidence, severity, affected objects and proposed follow-up. |
| Meaning knowledge record | data/knowledge MLE | personal Meaning maintenance | retrieval, reflection, review, Learning, profile-dispute context | conceptually approved | Preserves subject, evidence, contextual interpretation, provenance, confidence, status, scope, and revision without granting authority. |
| Learning knowledge record | data/knowledge MLE | evidence-linked Learning maintenance | retrieval, proposals, preferences, routines, workflows, agent-definition review | conceptually approved | A revisable lesson may inform later reasoning but cannot modify behavior or policy by itself. |
| Derived-representation registry record | data/operations MLE | derived-representation lifecycle governance | derivation, retrieval, knowledge compilation, portability, deletion, integrity assessment | conceptually approved | Distinguishes source/version, representation identity, processing provenance, authorization, lifecycle, replacement, and physical reference. |
| Artifact-promotion record | data/governance MLE | canonical artifact promotion | execution workspaces, results, knowledge compilation, canonical object revision, cleanup, History | conceptually approved | Records candidate artifact, source work, target canonical object/version, review/approval, transformations, conflicts, verification, and disposition. |