{
  "schemaVersion": 1,
  "generatedFrom": "src/data/catalogue.js",
  "wiki": {
    "title": "Co.Property internal wiki",
    "version": "2026.10.20.2",
    "date": "20 October 2026"
  },
  "page": {
    "stableId": "glossary#page",
    "pageId": "glossary",
    "pageTitle": "Glossary: use words that preserve the decision boundary",
    "pageSlug": "reference/glossary",
    "sectionId": "page",
    "sectionTitle": "Glossary: use words that preserve the decision boundary",
    "sectionProse": [
      "Shared terms make handovers safer. The most important distinctions are record versus task versus knowledge, source versus projection, and assigned versus evidenced versus accepted.",
      "Give nontechnical readers a compact vocabulary that keeps status labels honest and makes an operational question easier to investigate.",
      "A source record leads to a task. The task produces evidence. A verifier accepts or rejects the outcome. Knowledge explains how the cycle should work next time.",
      "Core terms: record, task, knowledge, source, and projection",
      "A record describes something, such as a property, reservation, owner relationship, subscription, or decision. A task is an accountable next action with a responsible person, due time, and verifiable outcome. Knowledge is a reusable explanation, such as an SOP, incident lesson, report interpretation, or decision note.",
      "A source is the authority for a specific observation or transaction. A projection is a distributed or displayed view of information from another writer. Naming both prevents a dashboard card or cache from becoming an accidental source of truth.",
      "A worktree is a separate working copy for one change, so edits do not disturb the installed application. A regression test checks that existing behavior still works after a change. A fixture is a controlled example, such as a duplicated message or failed provider response, used to check that behavior safely.",
      "A pull request (PR) asks someone to review a proposed code change before it joins the shared version. A release is the separate step of putting reviewed changes into the running system. Passing tests and merging a PR do not by themselves prove a release is installed or working for staff.",
      "State labels: assigned, in progress, evidenced, accepted, and exception",
      "Assigned means a person has an expected next action. In progress means work is underway. Evidence received means a result has been supplied and can be checked. Accepted means an authorised verifier recorded a supported outcome. An exception means a known gap, mismatch, or stale source still needs ownership.",
      "These labels should not be collapsed. A completed cleaning task can remain unverified; a recently opened dashboard can remain stale; a connected adapter can remain unaccepted. Precise labels help the next person make the right decision.",
      "Say what is known, pending, and proposed",
      "Use Checked for a specific documented or verified item and In progress for unfinished evidence, acceptance, or recovery work. The current wiki deliberately keeps turnover evidence, LINE acceptance, provider freshness, and cold boot recovery visible as pending.",
      "Avoid words such as “live”, “complete”, or “confirmed” unless the relevant source and reviewer support them. A concise, honest status helps more than a broad reassuring statement."
    ],
    "version": "2026.10.20.2",
    "date": "20 October 2026",
    "status": "Checked",
    "currentStatus": "Checked — terms are defined from the approved operating model and architecture without exposing private record detail.",
    "proposedStatus": "Add a term only when it clarifies an approved boundary; avoid jargon that conceals uncertainty.",
    "expectedOutcome": "A reader can choose a precise label for what is known, what must happen next, and what still needs acceptance.",
    "tests": [
      "Check glossary terms match the labels used in diagrams, search, and contextual exports.",
      "Check state terms do not imply completion where evidence or acceptance is pending."
    ],
    "sourcePointers": [
      "docs/OS-CORE.md",
      "docs/OS-SECTIONS.md",
      "docs/CONNECTOR-CONTRACTS.md",
      "coprop_kb/company_os.py",
      "coprop_kb/workflows.py",
      "Handoff / pages/organisation.html",
      "Handoff / pages/workflows.html",
      "Handoff / pages/infrastructure.html"
    ],
    "related": [
      {
        "id": "company-os",
        "title": "The Company OS: five connected responsibilities",
        "summary": "Managing, Selling, Planning, Delivering, and Learning are operational concepts for seeing the same company picture. They are not an invented staff chart.",
        "status": "Checked",
        "path": "/company-os/"
      },
      {
        "id": "turnover",
        "title": "Turnover readiness: evidence before a ready decision",
        "summary": "A turnover prepares a property between stays. Assignment, cleaning completion, evidence, verification, and readiness are separate states that must refer to the same confirmed property.",
        "status": "In progress",
        "path": "/workflows/turnover-evidence/"
      },
      {
        "id": "data-replicas",
        "title": "Provider → data → replica: one writer, protected projections",
        "summary": "Providers remain authoritative for their own transactions. The main mini writes internal company state; Cloudflare protected replicas and the Vercel staff PWA consume projections rather than replacing the master record.",
        "status": "Checked",
        "path": "/systems/data-replicas/"
      }
    ],
    "sshTarget": {
      "alias": "coproperty-office",
      "hostname": "copropertys-mac-mini.tail3ab9e5.ts.net",
      "user": "coproperty",
      "projectPath": "/Users/coproperty/Projects/coproperty-office-os",
      "codexPath": "/Users/coproperty/.local/bin/codex",
      "hostFingerprint": "SHA256:UUFmlsdclEmRtyRWNqAdVYUoFxeUkRUGhbzObQPsOPg",
      "requiredChecks": [
        "Verify the hostname, project path, and repository status before any work.",
        "Create an isolated task worktree outside the installed project.",
        "Never modify the installed runtime from this contribution path."
      ]
    }
  },
  "sections": {
    "terms": {
      "stableId": "glossary#terms",
      "pageId": "glossary",
      "pageTitle": "Glossary: use words that preserve the decision boundary",
      "pageSlug": "reference/glossary",
      "sectionId": "terms",
      "sectionTitle": "Core terms: record, task, knowledge, source, and projection",
      "sectionProse": [
        "A record describes something, such as a property, reservation, owner relationship, subscription, or decision. A task is an accountable next action with a responsible person, due time, and verifiable outcome. Knowledge is a reusable explanation, such as an SOP, incident lesson, report interpretation, or decision note.",
        "A source is the authority for a specific observation or transaction. A projection is a distributed or displayed view of information from another writer. Naming both prevents a dashboard card or cache from becoming an accidental source of truth.",
        "A worktree is a separate working copy for one change, so edits do not disturb the installed application. A regression test checks that existing behavior still works after a change. A fixture is a controlled example, such as a duplicated message or failed provider response, used to check that behavior safely.",
        "A pull request (PR) asks someone to review a proposed code change before it joins the shared version. A release is the separate step of putting reviewed changes into the running system. Passing tests and merging a PR do not by themselves prove a release is installed or working for staff."
      ],
      "version": "2026.10.20.2",
      "date": "20 October 2026",
      "status": "Checked",
      "currentStatus": "Checked — the terms come from the documented company model and infrastructure boundary.",
      "proposedStatus": "Use the terms consistently in navigation, UI labels, prompts, and PR descriptions.",
      "expectedOutcome": "Readers can tell whether they need to inspect a fact, perform work, follow a procedure, or investigate a display.",
      "tests": [
        "Check local search returns each term using text-only results.",
        "Check generated Markdown includes the same term definitions as the page."
      ],
      "sourcePointers": [
        "docs/OS-CORE.md",
        "docs/OS-SECTIONS.md",
        "docs/CONNECTOR-CONTRACTS.md",
        "coprop_kb/company_os.py",
        "coprop_kb/workflows.py",
        "Handoff / pages/organisation.html",
        "Handoff / pages/workflows.html",
        "Handoff / pages/infrastructure.html"
      ],
      "related": [
        {
          "id": "company-os",
          "title": "The Company OS: five connected responsibilities",
          "summary": "Managing, Selling, Planning, Delivering, and Learning are operational concepts for seeing the same company picture. They are not an invented staff chart.",
          "status": "Checked",
          "path": "/company-os/"
        },
        {
          "id": "turnover",
          "title": "Turnover readiness: evidence before a ready decision",
          "summary": "A turnover prepares a property between stays. Assignment, cleaning completion, evidence, verification, and readiness are separate states that must refer to the same confirmed property.",
          "status": "In progress",
          "path": "/workflows/turnover-evidence/"
        },
        {
          "id": "data-replicas",
          "title": "Provider → data → replica: one writer, protected projections",
          "summary": "Providers remain authoritative for their own transactions. The main mini writes internal company state; Cloudflare protected replicas and the Vercel staff PWA consume projections rather than replacing the master record.",
          "status": "Checked",
          "path": "/systems/data-replicas/"
        }
      ],
      "sshTarget": {
        "alias": "coproperty-office",
        "hostname": "copropertys-mac-mini.tail3ab9e5.ts.net",
        "user": "coproperty",
        "projectPath": "/Users/coproperty/Projects/coproperty-office-os",
        "codexPath": "/Users/coproperty/.local/bin/codex",
        "hostFingerprint": "SHA256:UUFmlsdclEmRtyRWNqAdVYUoFxeUkRUGhbzObQPsOPg",
        "requiredChecks": [
          "Verify the hostname, project path, and repository status before any work.",
          "Create an isolated task worktree outside the installed project.",
          "Never modify the installed runtime from this contribution path."
        ]
      }
    },
    "state-labels": {
      "stableId": "glossary#state-labels",
      "pageId": "glossary",
      "pageTitle": "Glossary: use words that preserve the decision boundary",
      "pageSlug": "reference/glossary",
      "sectionId": "state-labels",
      "sectionTitle": "State labels: assigned, in progress, evidenced, accepted, and exception",
      "sectionProse": [
        "Assigned means a person has an expected next action. In progress means work is underway. Evidence received means a result has been supplied and can be checked. Accepted means an authorised verifier recorded a supported outcome. An exception means a known gap, mismatch, or stale source still needs ownership.",
        "These labels should not be collapsed. A completed cleaning task can remain unverified; a recently opened dashboard can remain stale; a connected adapter can remain unaccepted. Precise labels help the next person make the right decision."
      ],
      "version": "2026.10.20.2",
      "date": "20 October 2026",
      "status": "Checked",
      "currentStatus": "Checked — labels preserve the documented turnover and freshness decision boundaries.",
      "proposedStatus": "Use fixtures to keep UI labels accurate when a workflow changes.",
      "expectedOutcome": "Status language becomes a reliable pointer to evidence, not a substitute for it.",
      "tests": [
        "Test states where work is complete but evidence is missing, and where source is stale but screen is recent.",
        "Check no state label silently becomes accepted without verifier input."
      ],
      "sourcePointers": [
        "docs/OS-CORE.md",
        "docs/OS-SECTIONS.md",
        "docs/CONNECTOR-CONTRACTS.md",
        "coprop_kb/company_os.py",
        "coprop_kb/workflows.py",
        "Handoff / pages/organisation.html",
        "Handoff / pages/workflows.html",
        "Handoff / pages/infrastructure.html"
      ],
      "related": [
        {
          "id": "company-os",
          "title": "The Company OS: five connected responsibilities",
          "summary": "Managing, Selling, Planning, Delivering, and Learning are operational concepts for seeing the same company picture. They are not an invented staff chart.",
          "status": "Checked",
          "path": "/company-os/"
        },
        {
          "id": "turnover",
          "title": "Turnover readiness: evidence before a ready decision",
          "summary": "A turnover prepares a property between stays. Assignment, cleaning completion, evidence, verification, and readiness are separate states that must refer to the same confirmed property.",
          "status": "In progress",
          "path": "/workflows/turnover-evidence/"
        },
        {
          "id": "data-replicas",
          "title": "Provider → data → replica: one writer, protected projections",
          "summary": "Providers remain authoritative for their own transactions. The main mini writes internal company state; Cloudflare protected replicas and the Vercel staff PWA consume projections rather than replacing the master record.",
          "status": "Checked",
          "path": "/systems/data-replicas/"
        }
      ],
      "sshTarget": {
        "alias": "coproperty-office",
        "hostname": "copropertys-mac-mini.tail3ab9e5.ts.net",
        "user": "coproperty",
        "projectPath": "/Users/coproperty/Projects/coproperty-office-os",
        "codexPath": "/Users/coproperty/.local/bin/codex",
        "hostFingerprint": "SHA256:UUFmlsdclEmRtyRWNqAdVYUoFxeUkRUGhbzObQPsOPg",
        "requiredChecks": [
          "Verify the hostname, project path, and repository status before any work.",
          "Create an isolated task worktree outside the installed project.",
          "Never modify the installed runtime from this contribution path."
        ]
      }
    },
    "language-discipline": {
      "stableId": "glossary#language-discipline",
      "pageId": "glossary",
      "pageTitle": "Glossary: use words that preserve the decision boundary",
      "pageSlug": "reference/glossary",
      "sectionId": "language-discipline",
      "sectionTitle": "Say what is known, pending, and proposed",
      "sectionProse": [
        "Use Checked for a specific documented or verified item and In progress for unfinished evidence, acceptance, or recovery work. The current wiki deliberately keeps turnover evidence, LINE acceptance, provider freshness, and cold boot recovery visible as pending.",
        "Avoid words such as “live”, “complete”, or “confirmed” unless the relevant source and reviewer support them. A concise, honest status helps more than a broad reassuring statement."
      ],
      "version": "2026.10.20.2",
      "date": "20 October 2026",
      "status": "In progress",
      "currentStatus": "In progress — the listed operational areas need current real-world evidence before any broader completion language is justified.",
      "proposedStatus": "Update only the specific status that new evidence supports, with source and reviewer in the authorised record.",
      "expectedOutcome": "Readers do not mistake documentation coverage for operational completion.",
      "tests": [
        "Check all pages render only Checked or In progress human-status badges.",
        "Check pending topics remain pending in llms.txt and per-page context exports."
      ],
      "sourcePointers": [
        "docs/OS-CORE.md",
        "docs/OS-SECTIONS.md",
        "docs/CONNECTOR-CONTRACTS.md",
        "coprop_kb/company_os.py",
        "coprop_kb/workflows.py",
        "Handoff / pages/organisation.html",
        "Handoff / pages/workflows.html",
        "Handoff / pages/infrastructure.html"
      ],
      "related": [
        {
          "id": "company-os",
          "title": "The Company OS: five connected responsibilities",
          "summary": "Managing, Selling, Planning, Delivering, and Learning are operational concepts for seeing the same company picture. They are not an invented staff chart.",
          "status": "Checked",
          "path": "/company-os/"
        },
        {
          "id": "turnover",
          "title": "Turnover readiness: evidence before a ready decision",
          "summary": "A turnover prepares a property between stays. Assignment, cleaning completion, evidence, verification, and readiness are separate states that must refer to the same confirmed property.",
          "status": "In progress",
          "path": "/workflows/turnover-evidence/"
        },
        {
          "id": "data-replicas",
          "title": "Provider → data → replica: one writer, protected projections",
          "summary": "Providers remain authoritative for their own transactions. The main mini writes internal company state; Cloudflare protected replicas and the Vercel staff PWA consume projections rather than replacing the master record.",
          "status": "Checked",
          "path": "/systems/data-replicas/"
        }
      ],
      "sshTarget": {
        "alias": "coproperty-office",
        "hostname": "copropertys-mac-mini.tail3ab9e5.ts.net",
        "user": "coproperty",
        "projectPath": "/Users/coproperty/Projects/coproperty-office-os",
        "codexPath": "/Users/coproperty/.local/bin/codex",
        "hostFingerprint": "SHA256:UUFmlsdclEmRtyRWNqAdVYUoFxeUkRUGhbzObQPsOPg",
        "requiredChecks": [
          "Verify the hostname, project path, and repository status before any work.",
          "Create an isolated task worktree outside the installed project.",
          "Never modify the installed runtime from this contribution path."
        ]
      }
    }
  }
}