Co.PropertyTeam wikiCo.Property20 October 2026
Press slash to search. Arrow keys select a result.
Internal knowledge
Browse the wiki

Systems

Data & replicas

Checked

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.

Download page Markdown
Interactive mapSelect a node to read its explanation. Use Work on this beside the section to prepare a change.
Provider → data → replica: one writer, protected projections diagramHospitable, Turno, and PriceLabs provide their own authoritative observations. The main mini writes internal company state and publishes protected Cloudflare replicas. The Vercel staff PWA and passive TV consume projections. Hermes is a separate adapter boundary.Providers — Provider → data → replica: one writer, protected projectionsProvidersMain mini writer — The Mac mini: authoritative writer and local operating coreMain mini writerCloudflare replicas — Provider → data → replica: one writer, protected projectionsCloudflare replicasVercel staff PWA — Dashboard and passive TV: shared views, not source authorityVercel staff PWAPassive TV — Dashboard and passive TV: shared views, not source authorityPassive TVHermes adapter — Hermes: an adapter boundary, not a company identityHermes adapter
Data moves from authoritative providers through the mini to protected projections.Solid · information flow
Read the diagram as text

Hospitable, Turno, and PriceLabs provide their own authoritative observations. The main mini writes internal company state and publishes protected Cloudflare replicas. The Vercel staff PWA and passive TV consume projections. Hermes is a separate adapter boundary.

  • Providers → Provider → data → replica: one writer, protected projections
  • Main mini writer → The Mac mini: authoritative writer and local operating core
  • Cloudflare replicas → Provider → data → replica: one writer, protected projections
  • Vercel staff PWA → Dashboard and passive TV: shared views, not source authority
  • Passive TV → Dashboard and passive TV: shared views, not source authority
  • Hermes adapter → Hermes: an adapter boundary, not a company identity
What it does

Make the provider-to-data-to-replica architecture legible, especially the difference between source freshness, publication success, and a recent dashboard repaint.

Responsibility

Hospitable, Turno, and PriceLabs remain authoritative for their own supported observations and transactions.

Next step

Name the authoritative provider for every provider-originating field.

Provider observations and company state travel through different responsibilities

Checked

Company documents provide business context.

Read the details

Company documents provide business context. Hospitable, Turno, and PriceLabs provide supported observations, while each provider remains authoritative for its own transactions. The main mini writes the internal tasks, decisions, identity links, and audit state that connect those observations to company work.

Cloudflare Worker, D1, and KV distribute protected replicated data and selected summaries. The Vercel staff PWA and passive TV consume these projections. Replicas and caches can be useful, but they are not the master record.

Current
Checked — this is the stated architecture boundary, not a claim about every individual field or live deployment.
Proposed next state
Document source ownership and publication behavior when adding a provider, field, or projection.
Expected outcome
A change proposal can preserve source authority and avoid a competing writer.
Checks to include when changing this section
  • Check every diagram node has a text-equivalent and focused-page link.
  • Check architecture exports mention the mini, Cloudflare, and Vercel roles without credentials.

Freshness requires a complete read and successful publication

In progress

Freshness means the relevant source window was read completely and then published successfully.

Read the details

Freshness means the relevant source window was read completely and then published successfully. It is not established by a recent screen repaint, a reopened browser tab, or a timestamp without source coverage context.

The data-health screenshot is a dated example that shows why labels such as live, unverified, stale, or reconciled need interpretation. It does not prove current provider freshness on its own.

Current
In progress — provider freshness must be verified against current source windows and publication evidence.
Proposed next state
Use explicit freshness fixtures and show the source-read and publication outcome in the relevant staff view.
Expected outcome
A user can ask whether data is current enough for the decision at hand instead of assuming it is.
Checks to include when changing this section
  • Run complete, stale, incomplete, and failed-publication fixtures.
  • Assert a screen repaint alone never changes a stale state to fresh.

Protected replicas improve access without changing authority

Checked

Protected replicas let staff use a dashboard without each person operating the mini.

Read the details

Protected replicas let staff use a dashboard without each person operating the mini. This is a distribution benefit, not a reason to move company writes into a cache, replica, or client surface.

When a projection disagrees with a source, investigate the source read, identity mapping, publication result, and exception owner. Do not quietly patch the replica and lose the underlying cause.

Current
Checked — the documented design separates writing from protected projection consumption.
Proposed next state
Keep access protection, source pointers, and refresh semantics explicit as new views are added.
Expected outcome
The architecture stays understandable under failure, not only when a dashboard looks normal.
Checks to include when changing this section
  • Check a replica-disagreement fixture opens an investigation path rather than a direct data edit.
  • Check no generated prompt asks for a token or a production write.

Apply with care

A concrete safe example

Example, responsibilities & checklist

A freshness-safe investigation

If a dashboard says a provider snapshot is recent, inspect the source-window result and publication result before trusting it. A reopened tab or a newly painted card is not a complete source read.

Responsibilities

  • Hospitable, Turno, and PriceLabs remain authoritative for their own supported observations and transactions.
  • The main mini writes internal tasks, decisions, identity links, and audit state.
  • Cloudflare Worker, D1, and KV hold protected replicated data and selected summaries.
  • The Vercel staff PWA consumes projections; it does not become the master record.

Checklist

  1. Name the authoritative provider for every provider-originating field.
  2. Distinguish a source read from publication to a protected replica.
  3. Show stale, failed, duplicate, and unresolved-identity conditions visibly.
  4. Do not use a cache, replica, or freshly opened screen as freshness proof.
Expected outcome

A reader can identify the source, writer, replica, consumer, and freshness condition behind an operational view.

Traceability without sensitive material

Source pointers and exports

This page expands the approved handoff into plain-language guidance. It does not include runtime logs, credentials, databases, private evidence, internal QA artifacts, or developer planning history.

Documentation references
  • Handoff / pages/infrastructure.html
  • Handoff / pages/app-tour.html
  • Handoff / START-HERE.html
Page MarkdownPage context JSON