# Co.Property internal wiki

A practical, plain-language guide to Co.Property’s operating model, systems, workflows, and safe contribution path.

Version: 2026.10.20.2
Date: 20 October 2026
Scope: Static internal orientation. No execution API, credentials, runtime logs, or private evidence.

## Pages
- [Start with the operating picture](/) — 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. (In progress)
- [The Company OS: five connected responsibilities](/company-os/) — Managing, Selling, Planning, Delivering, and Learning are operational concepts for seeing the same company picture. They are not an invented staff chart. (Checked)
- [Property lifecycle: from enquiry to review](/workflows/property-lifecycle/) — 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. (Checked)
- [Turnover readiness: evidence before a ready decision](/workflows/turnover-evidence/) — 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. (In progress)
- [Finance records: support the review before the conclusion](/workflows/finance-records/) — Financial planning and settlement work need identifiable source records, clear commitments, authorised review, and a traceable link to any learning that follows. (Checked)
- [SOP learning: turn observations into a better next step](/workflows/sop-learning/) — Learning connects incidents, reports, and repeated exceptions to a reviewed procedure. It prevents a useful lesson from being stranded in a one-off conversation. (Checked)
- [LINE boundaries: separate identities, accepted records, clear limits](/workflows/line-boundaries/) — LINE employee operations bot, Hermes adapter, and company Official Account are separate identities. A message flow only becomes operational evidence when the right record and acceptance boundary are confirmed. (In progress)
- [Dashboard and passive TV: shared views, not source authority](/systems/dashboard-and-tv/) — The staff dashboard and passive TV surfaces make a shared operating picture visible. They consume projections; they do not become the authoritative writer for company state. (Checked)
- [The Mac mini: authoritative writer and local operating core](/systems/mac-mini/) — The office Mac mini holds internal company state and runs configured operating processes. It is the authoritative writer for internal tasks, decisions, identity links, and audit state. (Checked)
- [Provider → data → replica: one writer, protected projections](/systems/data-replicas/) — 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. (Checked)
- [Hermes: an adapter boundary, not a company identity](/systems/hermes/) — Hermes is an adapter in the operating architecture. It does not replace the company Official Account, employee operations bot, provider authority, or a reviewed record boundary. (In progress)
- [Personal access: choose the least-privileged path](/contribution/access/) — 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. (Checked)
- [Contribution: isolated workspaces, meaningful tests, reviewed release](/contribution/workspace-and-pr/) — 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. (Checked)
- [Service directory: approved destinations, not shared access](/reference/service-directory/) — This directory names the approved service destinations used around Co.Property. Every destination requires an existing authorised account or approved auth; the wiki never stores tokens, credentials, or private logs. (Checked)
- [Glossary: use words that preserve the decision boundary](/reference/glossary/) — Shared terms make handovers safer. The most important distinctions are record versus task versus knowledge, source versus projection, and assigned versus evidenced versus accepted. (Checked)
- [Screenshots tour: dated examples, safer next questions](/reference/screenshots-tour/) — These sanitized screenshots are a visual orientation to the installed app captured on 20 October 2026. They are not mockups, credentials, or current operational proof. (Checked)

## Reading notes
- The five areas are operational concepts, not a confirmed staff reporting chart.
- The main mini owns writes; Cloudflare protected replicas and the Vercel staff PWA consume projections.
- Pending items are turnover evidence/verifier acceptance, LINE acceptance/final ownership, current provider freshness, and FileVault cold-boot recovery.
- Each page has a Markdown and context export in /exports/.