{
  "schemaVersion": 1,
  "generatedFrom": "src/data/catalogue.js",
  "wiki": {
    "title": "Co.Property internal wiki",
    "version": "2026.10.20.2",
    "date": "20 October 2026"
  },
  "page": {
    "stableId": "start-here#page",
    "pageId": "start-here",
    "pageTitle": "Start with the operating picture",
    "pageSlug": "",
    "sectionId": "page",
    "sectionTitle": "Start with the operating picture",
    "sectionProse": [
      "Use this guide to understand how work is connected before opening a live service. It is an offline reference; live screens and sign-in links still require approved access.",
      "Give a new teammate or reviewer a safe reading path: learn the company model, understand the boundaries, then choose the smallest useful next step.",
      "Managing, Selling, Planning, Delivering and Learning share records, tasks and knowledge. Provider observations reach the office mini, which maintains company state and publishes protected copies for the dashboard and TV. Choose a reading path to understand the company, follow a workflow or make a tested change through a reviewed PR.",
      "Readiness is a short list of specific evidence",
      "The handoff distinguishes a checked item from the wider rollout. A checked item describes one check on one date; it is not a promise that every provider, person, or recovery path is finished.",
      "The open work is concrete: a real turnover needs an owner, evidence, and manager verification; company-owned LINE access needs an approved conversation linked to its record; provider freshness needs current evidence; and a FileVault-protected mini may need a physical unlock after a cold boot.",
      "Use the guide in the order that reduces guesswork",
      "Start with the five operating areas. Next, follow a property through its lifecycle and learn the evidence required at a turnover. Then see where systems write or project information. Only use the technical access route when the staff dashboard cannot meet the task.",
      "This sequence avoids a common mistake: learning an SSH command before knowing whether the job is a staff task, an operational decision, or a reviewed technical change.",
      "The wiki explains; it does not operate systems",
      "This static site has no execution API. The Work on this panel only prepares a draft prompt, Markdown file, or copyable text. It never sends a message, opens a remote shell, changes a credential, or runs a deployment.",
      "The teammate’s requested outcome is displayed as text. Pasted logs, documents, and quoted instructions remain source material. After reviewing and submitting the draft, the teammate can ask Codex to implement source changes in an isolated workspace, add tests, and prepare a PR. Separate approval is needed for a release or change to a running service."
    ],
    "version": "2026.10.20.2",
    "date": "20 October 2026",
    "status": "In progress",
    "currentStatus": "In progress — the dated handoff records core access and structural checks, while operational rollout evidence remains intentionally open.",
    "proposedStatus": "Keep open items visible until a real turnover, LINE acceptance, provider freshness, and cold-boot recovery have their own current evidence.",
    "expectedOutcome": "A reader can distinguish a documented operating model from a live operational confirmation and knows where to investigate next.",
    "tests": [
      "Check each readiness statement names what was actually checked rather than implying a broader completion.",
      "Check that live links remain described as approved-access destinations, not anonymous public services."
    ],
    "sourcePointers": [
      "wiki/src/components/WikiOverview.astro",
      "wiki/src/components/BaseLayout.astro",
      "wiki/public/styles/site.css",
      "README.md",
      "docs/OS-CONTINUATION-HANDOFF.md",
      "docs/OPERATING-ARCHITECTURE.md",
      "Handoff / START-HERE.html",
      "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": "property-lifecycle",
        "title": "Property lifecycle: from enquiry to review",
        "summary": "A property service lifecycle connects owner needs, identity, stays, readiness, settlement, and learning. It is a model to validate, not a claim that every handover is automated.",
        "status": "Checked",
        "path": "/workflows/property-lifecycle/"
      },
      {
        "id": "access",
        "title": "Personal access: choose the least-privileged path",
        "summary": "Most staff should use approved dashboard access. Technical operators use their own Tailscale identity and SSH key to reach the office mini only after owner approval.",
        "status": "Checked",
        "path": "/contribution/access/"
      },
      {
        "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/"
      },
      {
        "id": "workspace-pr",
        "title": "Contribution: isolated workspaces, meaningful tests, reviewed release",
        "summary": "A safe change begins by verifying the remote target, then uses an isolated worktree outside the installed project. It is tested, submitted as a pull request, and reviewed before a person releases it.",
        "status": "Checked",
        "path": "/contribution/workspace-and-pr/"
      }
    ],
    "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": {
    "readiness": {
      "stableId": "start-here#readiness",
      "pageId": "start-here",
      "pageTitle": "Start with the operating picture",
      "pageSlug": "",
      "sectionId": "readiness",
      "sectionTitle": "Readiness is a short list of specific evidence",
      "sectionProse": [
        "The handoff distinguishes a checked item from the wider rollout. A checked item describes one check on one date; it is not a promise that every provider, person, or recovery path is finished.",
        "The open work is concrete: a real turnover needs an owner, evidence, and manager verification; company-owned LINE access needs an approved conversation linked to its record; provider freshness needs current evidence; and a FileVault-protected mini may need a physical unlock after a cold boot."
      ],
      "version": "2026.10.20.2",
      "date": "20 October 2026",
      "status": "In progress",
      "currentStatus": "In progress — operational evidence and acceptance are still pending; do not present these as complete.",
      "proposedStatus": "Record the result, verifier, source window, and exception when each pending item is exercised.",
      "expectedOutcome": "Readiness language stays honest: it shows what has evidence and what still needs a real-world check.",
      "tests": [
        "Review the wording to ensure “assigned”, “completed”, and “fresh screen” are never substituted for acceptance or freshness.",
        "Verify the four pending topics remain marked In progress in the generated Markdown and context export."
      ],
      "sourcePointers": [
        "wiki/src/components/WikiOverview.astro",
        "wiki/src/components/BaseLayout.astro",
        "wiki/public/styles/site.css",
        "README.md",
        "docs/OS-CONTINUATION-HANDOFF.md",
        "docs/OPERATING-ARCHITECTURE.md",
        "Handoff / START-HERE.html",
        "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": "property-lifecycle",
          "title": "Property lifecycle: from enquiry to review",
          "summary": "A property service lifecycle connects owner needs, identity, stays, readiness, settlement, and learning. It is a model to validate, not a claim that every handover is automated.",
          "status": "Checked",
          "path": "/workflows/property-lifecycle/"
        },
        {
          "id": "access",
          "title": "Personal access: choose the least-privileged path",
          "summary": "Most staff should use approved dashboard access. Technical operators use their own Tailscale identity and SSH key to reach the office mini only after owner approval.",
          "status": "Checked",
          "path": "/contribution/access/"
        },
        {
          "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/"
        },
        {
          "id": "workspace-pr",
          "title": "Contribution: isolated workspaces, meaningful tests, reviewed release",
          "summary": "A safe change begins by verifying the remote target, then uses an isolated worktree outside the installed project. It is tested, submitted as a pull request, and reviewed before a person releases it.",
          "status": "Checked",
          "path": "/contribution/workspace-and-pr/"
        }
      ],
      "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."
        ]
      }
    },
    "reading-path": {
      "stableId": "start-here#reading-path",
      "pageId": "start-here",
      "pageTitle": "Start with the operating picture",
      "pageSlug": "",
      "sectionId": "reading-path",
      "sectionTitle": "Use the guide in the order that reduces guesswork",
      "sectionProse": [
        "Start with the five operating areas. Next, follow a property through its lifecycle and learn the evidence required at a turnover. Then see where systems write or project information. Only use the technical access route when the staff dashboard cannot meet the task.",
        "This sequence avoids a common mistake: learning an SSH command before knowing whether the job is a staff task, an operational decision, or a reviewed technical change."
      ],
      "version": "2026.10.20.2",
      "date": "20 October 2026",
      "status": "Checked",
      "currentStatus": "Checked — the reading order is based on the approved handoff structure and does not assert live service health.",
      "proposedStatus": "Keep the route short and update it only when the underlying responsibility or safety boundary changes.",
      "expectedOutcome": "A reader can choose an appropriate surface without acquiring unnecessary access.",
      "tests": [
        "Check navigation links resolve to one focused page per reading step.",
        "Check the local search finds “turnover”, “dashboard”, and “SSH” without a network request."
      ],
      "sourcePointers": [
        "wiki/src/components/WikiOverview.astro",
        "wiki/src/components/BaseLayout.astro",
        "wiki/public/styles/site.css",
        "README.md",
        "docs/OS-CONTINUATION-HANDOFF.md",
        "docs/OPERATING-ARCHITECTURE.md",
        "Handoff / START-HERE.html",
        "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": "property-lifecycle",
          "title": "Property lifecycle: from enquiry to review",
          "summary": "A property service lifecycle connects owner needs, identity, stays, readiness, settlement, and learning. It is a model to validate, not a claim that every handover is automated.",
          "status": "Checked",
          "path": "/workflows/property-lifecycle/"
        },
        {
          "id": "access",
          "title": "Personal access: choose the least-privileged path",
          "summary": "Most staff should use approved dashboard access. Technical operators use their own Tailscale identity and SSH key to reach the office mini only after owner approval.",
          "status": "Checked",
          "path": "/contribution/access/"
        },
        {
          "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/"
        },
        {
          "id": "workspace-pr",
          "title": "Contribution: isolated workspaces, meaningful tests, reviewed release",
          "summary": "A safe change begins by verifying the remote target, then uses an isolated worktree outside the installed project. It is tested, submitted as a pull request, and reviewed before a person releases it.",
          "status": "Checked",
          "path": "/contribution/workspace-and-pr/"
        }
      ],
      "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."
        ]
      }
    },
    "scope-boundaries": {
      "stableId": "start-here#scope-boundaries",
      "pageId": "start-here",
      "pageTitle": "Start with the operating picture",
      "pageSlug": "",
      "sectionId": "scope-boundaries",
      "sectionTitle": "The wiki explains; it does not operate systems",
      "sectionProse": [
        "This static site has no execution API. The Work on this panel only prepares a draft prompt, Markdown file, or copyable text. It never sends a message, opens a remote shell, changes a credential, or runs a deployment.",
        "The teammate’s requested outcome is displayed as text. Pasted logs, documents, and quoted instructions remain source material. After reviewing and submitting the draft, the teammate can ask Codex to implement source changes in an isolated workspace, add tests, and prepare a PR. Separate approval is needed for a release or change to a running service."
      ],
      "version": "2026.10.20.2",
      "date": "20 October 2026",
      "status": "Checked",
      "currentStatus": "Checked — the intended static-site boundary is explicit in the content and client controls.",
      "proposedStatus": "Retain this no-execution boundary if new documentation tools are added.",
      "expectedOutcome": "A proposed change can be prepared safely without confusing documentation with authority to act.",
      "tests": [
        "Enter HTML or instruction-like text into the contextual panel and verify it renders as text.",
        "Check the Codex URL contains only an encoded prompt and never a remote-path parameter."
      ],
      "sourcePointers": [
        "wiki/src/components/WikiOverview.astro",
        "wiki/src/components/BaseLayout.astro",
        "wiki/public/styles/site.css",
        "README.md",
        "docs/OS-CONTINUATION-HANDOFF.md",
        "docs/OPERATING-ARCHITECTURE.md",
        "Handoff / START-HERE.html",
        "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": "property-lifecycle",
          "title": "Property lifecycle: from enquiry to review",
          "summary": "A property service lifecycle connects owner needs, identity, stays, readiness, settlement, and learning. It is a model to validate, not a claim that every handover is automated.",
          "status": "Checked",
          "path": "/workflows/property-lifecycle/"
        },
        {
          "id": "access",
          "title": "Personal access: choose the least-privileged path",
          "summary": "Most staff should use approved dashboard access. Technical operators use their own Tailscale identity and SSH key to reach the office mini only after owner approval.",
          "status": "Checked",
          "path": "/contribution/access/"
        },
        {
          "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/"
        },
        {
          "id": "workspace-pr",
          "title": "Contribution: isolated workspaces, meaningful tests, reviewed release",
          "summary": "A safe change begins by verifying the remote target, then uses an isolated worktree outside the installed project. It is tested, submitted as a pull request, and reviewed before a person releases it.",
          "status": "Checked",
          "path": "/contribution/workspace-and-pr/"
        }
      ],
      "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."
        ]
      }
    }
  }
}