{
  "_meta": {
    "type": "terms",
    "description": "Universal vocabulary for Leviathan Protocol governance. Federation coordination terms (instance, snapshot_hash, Sovereign Console, Constitutional Company, etc.) plus curated core-governance terms (consensus, the standing/enactment civic cascade, and the attestation-web / witness vocabulary). All domain instances inherit these terms.",
    "version": "2.1.0",
    "created": "2025-02-01",
    "updated": "2026-07-24",
    "project": "LEVIATHAN - Algorithmic Sovereignty for the Agentic Web",
    "changelog": "v2.1.0 (2026-07-23): Voice pass — re-anchored curated terms from the retired Magistrate verdict-engine to the federation attestation-web vocabulary (witnessed, append-only, replayable); removed XP / quadratic-voting language in favor of the standing/enactment civic cascade. v2.0.0 (2026-05-08): Added federation vocabulary — instance, snapshot_hash, forked_from, inherits_from, Sovereign Console, federation_member, Constitutional Company (new-structure + inversion patterns), dual-entity pattern, sibling-instance pattern, Lesson Ledger. Source: leviathan-meta/federation/terms.md (Layer 1). v1.1.0: Added verdict engine terms — blind evaluation, rounds, reasoning documents, approved models, node staking, dispute resolution, settlement, lazy detection, prompt injection.",
    "compiled_note": "Entries with source: federation:<repo> are compiled from the live federation constitutions by scripts/compile-federation-core.mjs — do not hand-edit them. Curated entries (no source field) are hand-maintained."
  },
  "@instance": {
    "version": "1.1.0",
    "domain": "federation",
    "definition": "A Leviathan-protocol-running entity that participates in the federation. Two kinds: L2 Sub-Leviathan (constitution-bearing — Markdown + YAML, no implementation code) and L3 Sub-Project (implementation bound to one L2 constitution). Each instance declares its kernel anchor.",
    "current_l2_constitutions_written": [
      "companion",
      "animal-welfare",
      "scream"
    ],
    "current_l2_seed_draft": [
      "medicine",
      "cyber-security"
    ],
    "current_l2_planned": [
      "tribun-leviathan"
    ],
    "current_l3_sub_projects": [
      "anima (impl: companion)",
      "tasma (impl: animal-welfare)"
    ],
    "instance_classes": [
      "L2 sub-leviathan (constitution)",
      "L3 sub-project (implementation)",
      "L3 fork (alternative implementation of same L2)"
    ]
  },
  "@snapshot_hash": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "SHA256 hash of an instance's constitution YAML, declared in instance manifest.yaml. Anchors a specific constitutional state in time.",
    "purpose": "Allows federation to verify instance constitutional integrity and detect drift",
    "computation": "Conformance tool walks constitution files, normalizes, hashes"
  },
  "@forked_from": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Required field in instance manifest.yaml declaring the kernel version this instance was forked from. Establishes provenance.",
    "current_anchor": "leviathan-kernel@v0.1.0",
    "discipline": "Per P-3, every member must declare this. Untracked-lineage instances cannot join."
  },
  "@inherits_from": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Optional field in instance manifest.yaml declaring a parent instance this constitution inherits from. null with re_anchor_seam:true is acceptable while master-leviathan@v0.1 is provisional.",
    "current_state": "All current instances declare null pending master-leviathan@v0.1 crystallization",
    "re_anchor_target": "master-leviathan@v0.1 (planned)"
  },
  "@re_anchor_seam": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Boolean flag in instance manifest.yaml indicating that inherits_from:null is provisional, not permanent — instance acknowledges it will re-anchor when target crystallizes.",
    "discipline": "Per kernel I-5, re_anchor_seam:true keeps the gap visible (honest provisional top) instead of pretending the instance is sovereign-by-default"
  },
  "@public_safe_manifest": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "An instance's curated public subset of its full constitution manifest. The full manifest may contain operational secrets (strategy params, threat intel, personal POS); the public-safe version is what federation can see.",
    "examples": [
      "companion/manifest-public.yaml (POS subset, no shadows/people)",
      "liveprob/manifest.yaml (no strategy edge)",
      "fast/manifest.yaml (no live trading params)"
    ],
    "implements_principle": "@p_2_privacy_sovereignty"
  },
  "@briefing": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "An append-only document filed in briefings/YYYY-MM-DD-name/ describing a cross-instance coordination event, kernel evolution, or amendment proposal.",
    "discipline": "Per P-5, briefings are append-only. If wrong, file corrective briefing alongside; do not edit original."
  },
  "@sovereign_console": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "leviathan-meta itself — a coordination instance that observes member instances without controlling them. Visibility primitive, NOT control primitive.",
    "implements_principle": "@p_6_sovereign_console_discipline",
    "kernel_reference": "kernel/03-constellation.md",
    "anti_pattern": "Using Sovereign Console to enforce specific instance behavior beyond status reporting (refutes federation purpose, see federation/manifest.yaml falsification claim)"
  },
  "@federation_member": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "An instance that has joined the federation by (a) creating a subdirectory in leviathan-meta, (b) filing status.md + manifest.yaml, (c) declaring kernel anchor, (d) submitting first-status briefing.",
    "membership_protocol": "federation/rules.md R-1 (Becoming a Federation Member)",
    "membership_implies": [
      "Subdirectory ownership discipline (P-1)",
      "Privacy bounds (control yours, do not violate others)",
      "Kernel anchor (forked_from is real)",
      "No silent override (surface discrepancies)",
      "Append-only briefings (do not rewrite history)",
      "Sovereign Console discipline (federation observes, does not control)"
    ],
    "no_central_approval": "Per P-2 sovereignty + P-8 fork freedom, no central approval required to join — founder may issue cautionary briefings but cannot prevent membership"
  },
  "@constitutional_company": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "A legal entity whose primary governance substrate is a constitutional system (terms, principles, rules, meta-rules) rather than classical equity/board hierarchy. Sovereign by design — cannot accept classical funding without losing Constitutional Company status.",
    "two_patterns": {
      "new_structure": "Build constitutional system where none existed (examples: ANIMA personal governance, Liveprob trade governance)",
      "inversion": "Replace existing power hierarchy with constitutional system (examples: Animal Welfare replacing classical pet industry, Fan-DAO replacing classical club management)"
    },
    "structural_distinction": "Inversion is structurally harder (incumbent resistance) but higher cultural impact when it lands"
  },
  "@dual_entity_pattern": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Architecture pattern where a Constitutional Company is paired with a classical SaaS product entity. Product can take classical funding; Constitutional Company cannot. Same data substrate, different governance/legal entities.",
    "examples": [
      "Tasma (product, classical) ↔ Animal Welfare (constitutional, inversion-CC)",
      "Tribün (product, global multi-sport SaaS) ↔ Fan-DAO (constitutional, inversion-CC)"
    ],
    "rationale": "Resolves apparent contradiction: classical funding incompatible with Constitutional Company status. Two entities, one data substrate, two governance modes."
  },
  "@sibling_instance_pattern": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Architecture pattern where two distinct federation instances are co-located on shared hardware/operator, specializing in different markets but sharing operational substrate. NOT the same as dual-entity (which is product/constitutional pair).",
    "current_example": "Mac Mini Liveprob+Fast duo — Liveprob (Polymarket prediction markets, paper-only) and Fast (Backpack maker-only Rust trading bot, live-money). Both Financial Leviathan instances, both Mac Mini-resident, different markets, different execution primitives, shared operator."
  },
  "@inversion_constitutional_company": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Subset of Constitutional Company that REPLACES an existing power hierarchy rather than building new structure. Higher cultural stakes, higher incumbent resistance.",
    "current_beachhead_candidates": [
      "Animal Welfare (replaces classical pet industry power)",
      "Fan-DAO (replaces classical club management — fans become governing body)"
    ],
    "falsification_claim": "If both Tasma → Animal Welfare AND Tribün → Fan-DAO fail to form their constitutional pair within 18 months, OR neither replaces incumbent hierarchy on at least one operational instance within 24 months, the inversion pattern is empirically refuted as generalizable."
  },
  "@lesson_ledger": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "Cross-instance pattern aggregation surface (planned, spec pending). Anonymized lessons from instance operations (e.g., what kinds of strategies fail constitution gates, what moderation decisions get flagged) feed back into kernel evolution.",
    "current_status": "Spec pending. Liveprob, Tribün, Fast, Security may opt into participation. Some instances (Fast) may decline due to strategy edge confidentiality concerns.",
    "kernel_reference": "kernel/03-constellation.md (Lesson Ledger as decentralization criterion #5)"
  },
  "@kernel_conformant_fork": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "An instance that forked from a kernel version and remains compliant with kernel immutables (I-1..I-5). Membership in federation is open to kernel-conformant forks.",
    "vs_divergent_fork": "Divergent forks reject kernel immutables; they cannot be federation members but can fork the federation itself"
  },
  "@divergent_fork": {
    "version": "1.0.0",
    "domain": "federation",
    "definition": "An instance or federation that forked from a parent but rejects parent's immutable layer. Sovereign by definition — not bound by parent's federation rules.",
    "freedom": "Per P-8 + kernel/03-constellation.md §6, fork freedom is absolute. Divergence is not betrayal."
  },
  "@personal_operating_system": {
    "version": "1.0.0",
    "domain": "federation",
    "abbreviation": "POS",
    "definition": "A person's versioned identity document. Tracks beliefs, principles, shadows (patterns to watch), and behavioral protocols across time. Edits create new versions; nothing is overwritten. Each version is timestamped with the trigger that produced it.",
    "shape": [
      "Concepts (@) — perceptual frames",
      "Principles (#) — guiding rules",
      "Actions (!) — active behavioral commitments",
      "Shadows (🜏) — repressed patterns under monitoring",
      "Protocols (⚙) — situational behavior sets"
    ],
    "ownership": "Lives on the user's machine. Federation never reads it directly. The 'master POS' is the founder's; everyone running a Companion has their own.",
    "rationale": "If your AI doesn't know who you are, it's working from a stranger's template. POS is the small file that fixes that — and fork freedom means you take it with you when you leave."
  },
  "@purpose": {
    "version": "1.0.0",
    "definition": "The stated goal that a Leviathan domain exists to serve.",
    "required": true,
    "examples": [
      "Protect AI agents from prompt injection and malicious commands",
      "Verify climate data and carbon offset claims"
    ]
  },
  "@citizen": {
    "version": "1.0.0",
    "definition": "Any entity (human or AI) participating in the Leviathan ecosystem with earned rights.",
    "types": [
      "human",
      "agent",
      "node"
    ],
    "note": "Citizenship is earned through contribution, not purchased."
  },
  "@prompt_injection_defense": {
    "version": "1.1.0",
    "definition": "Sanitization and isolation techniques that prevent malicious content in a submitted artifact from manipulating the witness node's LLM during evaluation.",
    "layers": {
      "size_limits": "Artifact text max 50 KB, attachments max 10 MB",
      "content_sanitization": "Strip HTML, JS, executable content, escape special characters",
      "pattern_detection": "Flag documents containing 'ignore previous instructions', 'you are now', 'system:', 'APPROVE this'",
      "prompt_isolation": "Artifact wrapped in clear delimiters with system prompt explicitly marking it as externally-submitted data",
      "output_validation": "Verify LLM output matches expected JSON schema, reject if reasoning contradicts the stated attestation"
    }
  },
  "@consensus": {
    "version": "1.2.0",
    "definition": "Collective agreement, measured differently depending on context.",
    "governance_thresholds": {
      "minor": 0.6,
      "major": 0.66,
      "constitutional": 0.75,
      "locked_principle": 0.95
    },
    "governance_mechanism": "Standing-weighted: eligibility and voice follow civic standing tier (earned through enactment), not token holdings — no quadratic or stake weighting.",
    "attestation_mechanism": "Within an audit, each independent witness stands on equal footing; disagreement widens review, it never narrows it."
  },
  "@domain": {
    "version": "1.0.0",
    "definition": "A specialized area within Leviathan with domain-specific rules.",
    "examples": [
      "security",
      "climate",
      "welfare",
      "finance"
    ]
  },
  "@fork": {
    "version": "1.0.0",
    "definition": "An independent copy of Leviathan with potential modifications.",
    "freedom": "Anyone may fork. No permission required.",
    "generator": "leviathan.life/fork"
  },
  "@dialectic": {
    "version": "1.0.0",
    "domain": "federation",
    "source": "federation:meta",
    "definition": "A structured discussion process to refine proposals through collaborative reasoning. A dialectic proceeds through three phases:\n\n1. Thesis — the original proposal, with evidence and justification. Authored by the proposer.\n2. Antithesis — counter-arguments, concerns, questions, and alternative views. Authored by the community. If, after the minimum 7-day discussion window, no substantive antithesis is raised, a moderator may log an explicit no_objections_logged entry in place of an antithesis post; silence alone is never a substitute.\n3. Synthesis — a refined proposal that incorporates valid concerns from the antithesis. Authored by the original proposer or any other participant. The synthesis must address every substantive antithesis before the proposal can advance to VOTING.\n\nMinimum total dialectic duration: 7 days. Dialectic happens in the federation forum board for the relevant Sub-Leviathan. No off-platform conversation, private channel, or external decision counts as constitutional dialectic. The thread is the record."
  },
  "@enactment": {
    "version": "1.0.0",
    "domain": "federation",
    "source": "federation:meta",
    "definition": "A numeric measure of a participant's accumulated constitutional enactment within the Leviathan federation. Every ratified proposal, accepted vote, witness attestation, or other recognized contribution is one enactment event — bringing a piece of constitutional intent into reality. Enactment is non-transferable (not a token, not currency), serves as the basis for advancing standing, and is recorded across all Sub-Leviathans the participant engages with."
  },
  "@evidence": {
    "version": "1.0.0",
    "domain": "federation",
    "source": "federation:meta",
    "definition": "Documentation supporting any factual claim in a proposal, antithesis, or synthesis. Evidence is classified into five quality tiers, each with an associated weight used by Sub-Leviathans when aggregating evidence in stratified reviews:\n\n| Tier | Name          | Description                                                         | Weight |\n|------|---------------|---------------------------------------------------------------------|--------|\n| S    | Systematic    | Peer-reviewed meta-analysis or systematic review                    | 1.0    |\n| A    | Academic      | Peer-reviewed primary research                                      | 0.8    |\n| B    | Institutional | Reports from recognized institutions (WHO, FAO, IEEE, NIST, etc.)   | 0.6    |\n| C    | Expert        | Expert opinion, grey literature, preprints                          | 0.4    |\n| D    | Anecdotal     | Personal observation, unverified claim                              | 0.1    |\n\nFederation-wide minimum for any proposal that modifies a factual claim: at least one source at Tier C or higher. Sub-Leviathans may declare a stricter minimum in their domain rules (Medicine, for example, may require Tier A for sentience claims). Sub-Leviathans may not lower this minimum below Tier C.\n\nCitation format (required): [Author (Year)] Title. Source. URL/DOI. The URL or DOI must resolve at the time of submission; broken links discovered later trigger an evidence-staleness flag (handled per Phase 2 amendment)."
  },
  "@proposal": {
    "version": "1.0.0",
    "domain": "federation",
    "source": "federation:meta",
    "definition": "A formal request to modify a constitutional element (term, principle, rule, shadow, protocol) in any Leviathan instance. Every proposal carries five required fields:\n\n- target — the slug of the element being changed, or a new slug if adding.\n- current_version — integer version of the target at submission time. For new elements: 0.\n- proposed_version — integer version after ratification. Must increment per rule_version_bump (Phase 2).\n- justification — the rationale: why this change serves the instance's purpose.\n- evidence — at least one source per the evidence term and rule_evidence_required.\n\nProposal lifecycle (linear, no skipping, no return-to-earlier-state except WITHDRAWN):\n\n\nDRAFT → DISCUSSION → VOTING → ACCEPTED | REJECTED | WITHDRAWN\n\n\n- DRAFT — authored and visible in the forum; evidence attached; awaiting transition to DISCUSSION.\n- DISCUSSION — open for rule_dialectic_format to apply; minimum 7 days; thesis/antithesis/synthesis recorded.\n- VOTING — opens only after synthesis posted; thresholds and quorum per Phase 2 amendment.\n- ACCEPTED — recorded in the append-only constitutional registry (forum-anchored today; on-chain anchoring is a declared, not-yet-live target); element's current_version updated.\n- REJECTED — vote failed; proposal closed with permanent record; new proposal may re-attempt.\n- WITHDRAWN — proposer (or successor with guardian standing) closes the proposal at any pre-VOTING stage.\n\nProposer must hold at least sentinel standing (see terms/standing). Proposal title format: [PROPOSAL] {action} @{target_slug} (v{current_version} → v{proposed_version})."
  },
  "@standing": {
    "version": "1.0.0",
    "domain": "federation",
    "source": "federation:meta",
    "definition": "A participant's civic position in the Leviathan federation, expressed as a tier. Standing carries different rights and responsibilities (vote, propose, validate, moderate). Standing is earned through enactment accumulation, never granted by edict. Current tiers (ascending): novice (signup default, reply-only) → sentinel (vote + propose) → guardian (board moderation) → arbiter (cross-domain authority)."
  },
  "@belief": {
    "version": "1.0.0",
    "domain": "companion",
    "source": "federation:companion",
    "definition": "A belief is an atomic unit of a user's personal governance — a single value, principle, or rule the user holds. Beliefs are typed (e.g., concept, axiom, directive) and editable; users add, modify, version, and retire their own beliefs over time. A user's full belief set IS their personal constitution."
  },
  "@persona": {
    "version": "1.0.0",
    "domain": "companion",
    "source": "federation:companion",
    "definition": "A persona is a sanitized, exportable representation of a user's belief system suitable for consent-mediated cross-user interaction. It encodes values, principle priorities, and behavioral preferences as a vector or structured object — not as raw journal content. The persona is derived from user beliefs by an on-device sanitization process; raw journal entries never become part of the persona."
  },
  "@sentience": {
    "version": "1.0.0",
    "domain": "animal-welfare",
    "source": "federation:animal-welfare",
    "definition": "The capacity to have subjective experiences and to feel valenced states such as pain, pleasure, or emotion. Sentience assessment is evidence-based across neurological, behavioral, and physiological indicators, with confidence levels HIGH/MEDIUM/LOW/UNKNOWN. UNKNOWN triggers the precautionary principle: protection is the default."
  },
  "@suffering": {
    "version": "1.0.0",
    "domain": "animal-welfare",
    "source": "federation:animal-welfare",
    "definition": "A prolonged negative affective state involving distress, pain, or deprivation. Distinct from brief acute pain (suffering persists beyond the immediate stimulus). Suffering is observable through behavioral, physiological, and (in some species) neurological indicators. Operational thresholds vary by species and context; uncertainty triggers the precautionary principle."
  },
  "@overton_shift": {
    "version": "1.0.0",
    "domain": "scream",
    "source": "federation:scream",
    "definition": "An Overton shift is the measurable change in the range of acceptable public discourse caused by sustained witness-amplification. A successful scream campaign produces conversations that were previously marginal becoming mainstream — not by manipulation, but by the cumulative weight of receipted documentation across a sustained period. Federation seeks specific Overton shifts (community-owned AI, federated governance, transparent mediation, witness epistemology) through patient witnessing, not single high-profile bursts."
  },
  "@scream": {
    "version": "1.0.0",
    "domain": "scream",
    "source": "federation:scream",
    "definition": "A scream is an amplified act of witness — a public communication of constitutionally-witnessed material delivered at volume calibrated to its stakes. Scream is loud where substance permits; deliberate, not reactive; sourced, not asserted. Distinct from noise (unsourced amplification), spam (unweighted volume), accusation (unilateral judgment), and silence (when amplification serves no constitutional purpose)."
  },
  "@algorithmic_fairness": {
    "version": "0.0.0",
    "domain": "medicine",
    "source": "federation:medicine",
    "status": "seed-draft",
    "definition": "@algorithmic-fairness in the Medicine Sub-Leviathan is the property of an AI tool that performs comparably across the patient populations it is deployed for. It is not satisfied by aggregate accuracy. A model that is 95% accurate overall but 60% accurate for women over 65, or for rural patients, or for any underrepresented group, fails algorithmic fairness regardless of its aggregate score.\n\nOperationally, fairness requires:\n\n1. Stratified performance reporting. Performance is reported separately for each clinically meaningful subgroup the tool is intended to serve.\n2. Subgroup floor. A minimum acceptable per-subgroup performance is defined before deployment, not after.\n3. Continuous monitoring. Fairness is re-measured in production, not just at validation. Drift in subgroup performance triggers review.\n4. Disclosure to clinician and patient. When a tool's performance is materially worse for the patient's subgroup, the physician knows and the patient is told."
  },
  "@clinical_decision": {
    "version": "0.0.0",
    "domain": "medicine",
    "source": "federation:medicine",
    "status": "seed-draft",
    "definition": "A @clinical-decision is any judgment that affects diagnosis, treatment, intervention, referral, deferral, or risk allocation for a specific patient. It is distinguished from:\n\n- Information lookup (the AI returns guideline content, drug interaction data, literature)\n- Triage suggestion (the AI orders a queue, surfaces a flag, scores urgency — without acting)\n- Administrative process (scheduling, billing, documentation generation)\n\nInformation lookup, triage suggestions, and administrative processes may be AI-mediated. Clinical decisions remain the licensed physician's. This is the boundary that 01-human-in-the-loop-authority enforces."
  },
  "@health_data_vs_ordinary_data": {
    "version": "0.0.0",
    "domain": "medicine",
    "source": "federation:medicine",
    "status": "seed-draft",
    "definition": "@health-data is the class of patient information that carries the patient's body, history, vulnerability, and intimate facts. It is not \"data\" in the generic governance sense; it inherits the more demanding standard of patient-physician confidentiality, applied uniformly across every system that touches it — clinical, AI training, secondary research, hospital analytics, downstream products.\n\nThis term distinguishes health data from ordinary data along four operational axes:\n\n1. Sensitivity asymmetry. A leak of ordinary data is reversible (passwords change, cards are reissued). A leak of health data — HIV status, mental-health history, genetic risk, abortion history — is permanent and follows the patient through employment, insurance, family relationships.\n2. Re-identification floor. \"Anonymized\" health data, especially genomic + longitudinal, is increasingly re-identifiable in modern AI contexts. Anonymization alone is not adequate governance.\n3. Consent inheritance. Consent for one use does not inherit to another. Consent for clinical care is not consent for training. Consent for one study is not consent for downstream model fine-tuning.\n4. Substrate continuity. As the substrate of experience becomes addressable (BCI, neurotech), neural data joins the health-data class. The term must be future-proof against that expansion."
  },
  "@informed_consent": {
    "version": "0.0.0",
    "domain": "medicine",
    "source": "federation:medicine",
    "status": "seed-draft",
    "definition": "@informed-consent in the AI-mediated medical context is consent that meets the classical informed-consent standard (capacity, disclosure, comprehension, voluntariness) and additionally the AI-era requirements:\n\n1. Disclosure of AI involvement. The patient is told which AI tool participates in their care, what role it plays (diagnostic, triage, suggestion, monitoring), and what its known uncertainty / failure modes are.\n2. Scope, duration, revocation. Consent for AI use in care is separately scoped from consent for AI training. Each scope is time-bound and revocable, with downstream cleanup obligations on every system that received the data.\n3. Comprehension does not require expertise. The disclosure must be in language the patient can understand, not in technical specification language. Comprehension is a clinical responsibility, not a documentation formality.\n4. No bundled consent. Consent for clinical care cannot be conditioned on consent for AI training or secondary research. Each is a separate decision."
  },
  "@medical_harm": {
    "version": "0.0.0",
    "domain": "medicine",
    "source": "federation:medicine",
    "status": "seed-draft",
    "definition": "@harm in the Medicine Sub-Leviathan denotes any AI-mediated outcome that injures the patient or the integrity of the physician-patient relationship. It is broader than physical injury and explicitly includes:\n\n- Clinical harm — incorrect diagnosis, missed finding, inappropriate treatment, delayed care.\n- Statistical harm — systematic underperformance for a specific population (rural, women, elderly, ethnic minority, low-income), even when aggregate accuracy is high.\n- Dignity harm — reduction of the patient to a data object; loss of the patient's voice in their own care.\n- Privacy harm — exposure, secondary use, or re-identification of patient health data outside consented scope.\n- Authority displacement harm — clinical decision effectively made by an opaque algorithm, with the physician serving as legal cover rather than accountable counterparty."
  },
  "@physician_irreducible": {
    "version": "0.0.0",
    "domain": "medicine",
    "source": "federation:medicine",
    "status": "seed-draft",
    "definition": "@physician-irreducible names the residue of clinical practice that AI cannot occupy without breaking the practice itself. It is the answer to: what makes the physician necessary, even when the AI is more accurate on average?\n\nThe seed claim — to be sharpened by the domain author — is that the irreducible residue includes:\n\n1. Accountable judgment. A licensed counterparty whose name attaches to the decision and who can be held to it (medically, legally, ethically). An algorithm cannot be held accountable in the way a person can.\n2. Contextual integration. Synthesis across the patient's narrative, family situation, values, fears, and unspoken cues — the parts that don't enter the structured record.\n3. Moral weight in the room. The physical presence of a person who carries the seriousness of the moment, especially in life-altering disclosures (cancer diagnosis, end-of-life decisions, irreversible interventions).\n4. Discretion to deviate. Authority to depart from the algorithmic recommendation when the patient in front of them is the exception the model didn't see.\n\nIf any of these four can be discharged by an AI without harm, that subspace is not physician-irreducible. The term is intentionally narrow: it carves the minimum, not the maximum, of what physicians do."
  },
  "@asset": {
    "version": "0.0.0",
    "domain": "cyber-security",
    "source": "federation:cyber-security",
    "status": "seed-draft",
    "definition": "An asset is anything under federation protection whose compromise would constitute harm. Assets include: information (data at rest, in transit, in compute), systems (hosts, services, accounts, credentials), processes (business workflows, governance procedures), and reputation (trust position with users, peers, regulators). Each asset has an owner (the participant responsible for it), a classification (sensitivity level), a dependency map (what other assets depend on it), and a protection floor (minimum controls required). An asset's compromise can be measured in confidentiality, integrity, availability, or reputational terms — the classical CIA triad expanded with reputation as a federation-relevant fourth."
  },
  "@incident": {
    "version": "0.0.0",
    "domain": "cyber-security",
    "source": "federation:cyber-security",
    "status": "seed-draft",
    "definition": "An incident is an observed event or sequence of events in which a threat has interacted with one or more assets in a way that violates federation security policy, regardless of whether harm was successfully realized. An incident has a timeline (when observed, when started, when contained, when closed), an attribution claim (the threat responsible, with confidence), an impact assessment (what was actually affected), and an evidence chain (the data supporting all of the above). Incidents are immutable once filed; corrections produce new versions, never overwrites."
  },
  "@threat": {
    "version": "0.0.0",
    "domain": "cyber-security",
    "source": "federation:cyber-security",
    "status": "seed-draft",
    "definition": "A threat is any actor, condition, or sequence of events with the intent and capacity to cause harm to an asset under federation protection. Threats are classified by source (external actor, insider, automated agent, environmental), by target (asset class), and by stage in the attack lifecycle (reconnaissance, exploitation, persistence, exfiltration, impact). A threat that has not yet materialized into an incident is still a threat; the absence of harm does not negate the classification."
  },
  "@vulnerability": {
    "version": "0.0.0",
    "domain": "cyber-security",
    "source": "federation:cyber-security",
    "status": "seed-draft",
    "definition": "A vulnerability is a property of an asset, configuration, or process that, if encountered by a threat, may enable harm. Vulnerabilities are properties — not events — and exist whether or not anyone has yet exploited them. Each vulnerability is characterized by: a target asset class, an exploitation pre-condition (what a threat needs to use it), an impact class (what harm follows exploitation), and a remediation pathway (how it can be reduced or eliminated)."
  }
}
