Protected CHC notebook

ops.curatedhomecleaning.ca

A protected CHC project notebook view over curated business continuity — designed to preserve project state, priorities, communication lanes, and recovery value without exposing local-only systems or unrelated Marcus-world context.

Notebook on the surface, CHC-scoped continuity underneath.

ExposureProtected Pages artifact
PurposeCHC continuity + execution
AuthCloudflare Access

Current focus

What matters right now

  • Make this CHC ops surface a clean notebook/dashboard instead of a fake chat shell.
  • Keep CHC continuity scoped to business operations, not Marcus-global/private context.
  • Preserve the request/status intermediary plan as a narrow next-step architecture.
  • Keep the public marketing site separate from this protected workspace.

Why this notebook exists

One CHC lane, one continuity spine

This page should act like the CHC equivalent of ops.bluegrouse.ai: a readable project notebook that shows current state, durable checkpoints, business systems direction, and the next safe move — without pretending unfinished chat features are already live.

Project state

Workspace roleProtected CHC notebook + ops surface
Current phaseNotebook/dashboard correction
Access postureCloudflare Access allowlist
Primary scopeCHC web, marketing, systems, admin

Recovery discipline

  • Canonical continuity stays local.
  • This page is a protected derived view, not the source of truth.
  • Important milestones should be checkpointed into CHC-scoped notes and task files.
  • Request/status interaction should use the narrow intermediary path, not broad gateway authority.

Local-only interfaces

  • Local CHC bridge: 127.0.0.1:4314
  • CHC intermediary: 127.0.0.1:4315
  • Canonical request log: data/chc-workspace/requests.json
  • Secrets stay in the local vault, not in this page.

Records

CHC notebook records

Checkpoint
CHC ops workspace and chat MVP

The protected CHC workspace became the intended primary Sasha-Agent surface for CHC business work, with Cloudflare Access hardened first and broader public chat surfaces rejected.

Source: tasks/open/chc-ops-workspace-and-chat-mvp-2026-04-01.md

Checkpoint
Browser-safe intermediary

A narrow intermediary path was chosen so the CHC page can capture requests and reflect recent status without exposing broad gateway/operator authority.

Source: tasks/open/chc-browser-safe-intermediary-2026-04-01.md

Decision
Google Chat direction for CHC conversation lane

Marcus chose Google Chat as the preferred regular conversation lane for CHC instead of a general-purpose web chat surface, while keeping this protected page narrower and operational.

Source: tasks/open/google-chat-chc-conversation-lane-2026-04-02.md

System
Twilio communications foundation

CHC already has working Twilio voice/SMS foundations and voicemail routing; this page should reflect that as part of the business systems picture rather than burying it behind unrelated UI experiments.

Source: tasks/open/curated-twilio-number-and-voicemail-foundation-2026-03-31.md

Architecture
Separation rule

The public CHC site owns the public marketing pages; this protected project owns only ops.curatedhomecleaning.ca.

Source: sites/ops.curatedhomecleaning.ca/README.md

Publishing model

This protected CHC page should be published as its own dedicated Pages project and stay focused on notebook-style business continuity, status, and safe next steps. It should not masquerade as finished live chat when that interaction layer is still under construction.

Next build step

After this notebook-style correction is live, the next safe product step is to add honest request/status modules backed by the CHC intermediary and local request log — preserving the same notebook structure instead of replacing it with a fake messenger UI.