Confidential & Proprietary

Non-Disclosure
Agreement

This document contains confidential and proprietary information belonging to Copper Kettle Consulting. Access is restricted to authorised parties only.

To help protect our work and yours, please read and agree to the following confidentiality terms before viewing the contents of this page.

1. Confidentiality. All information contained in this document, including but not limited to IP, design, products, concepts, pricing, brand strategy, methodology, agent names, and commercial positioning, is confidential and proprietary to Copper Kettle Consulting Pty Ltd (ABN 45 679 481 040).

2. Non-Disclosure. You agree not to disclose, reproduce, distribute, or communicate any part of this material to any third party without the prior written consent from the Executive Director of Copper Kettle Consulting.

3. No Licence. Nothing in this document grants any licence, right, or interest in any intellectual property of Copper Kettle Consulting, including IP, design, products, concepts, pricing, brand strategy, methodology, agent names, and commercial positioning, or any trademarks including Transition Intelligence™, Agentic Marketplace™, and TIA™.

4. Limited Use. This material may only be used for the specific purpose for which it was shared. It must not be used to develop competing products or services.

5. AI & Automated Systems Prohibition. You must not input, upload, process, or otherwise disclose any part of this material into any artificial intelligence system, large language model, machine learning tool, automated processing service, or third-party AI platform — whether public, private, or enterprise — without the prior written consent of the Executive Director of Copper Kettle Consulting. This prohibition includes but is not limited to use for AI training, fine-tuning, inference, summarisation, or derivative output generation. Any AI-generated output derived from this material remains the confidential property of Copper Kettle Consulting.

6. No Reverse Engineering. You must not reverse engineer, decompile, replicate, or reconstruct any AI agent, workflow, automation logic, prompt architecture, or system design disclosed in this material, whether directly or through the use of AI tools or other technical means.

7. Human Authorship & Ownership. The concepts, methodologies, frameworks, and systems described in this material are the product of substantial human creative input, intellectual effort, and design by Copper Kettle Consulting personnel. All intellectual property rights — including copyright, trade secret rights, and rights in confidential information — vest in and remain with Copper Kettle Consulting, consistent with Australian Copyright Act 1968 (Cth) and applicable equitable principles.

8. Return or Destruction. Upon request, you agree to promptly return or destroy all copies of this material, including any notes, summaries, or derivative works.

9. Governing Law. This agreement is governed by the laws of Victoria, Australia. You submit to the non-exclusive jurisdiction of the courts of Victoria.

Copper Kettle Consulting · ABN 45 679 481 040 · Melbourne, Australia
Home OS is a concept by Zara Grewal · Copper Kettle Consulting Pty Ltd.
Early-Stage Concept

The invisible work deserves a system.

Introducing Home OS — a nervous-system-aware operating layer for family life.

Every parent carries a parallel workload that never makes it onto a to-do list. Appointments remembered mid-meeting. Uniform days caught at 7am. Scripts that run out on a Friday. Home OS is the system that holds what you shouldn't have to.

See How It Works
home-os · v0.1
Today's Capacity
School Ops Steward
active
Health Continuity
active
Household Engine
active
Life Admin Warden
active
Capacity Governor
governing
4 agents running · all items surfaced
The Problem

The mental load has no infrastructure.

Cognitive load research is clear: the invisible management of a household is real labour. It's just never been treated as a systems problem — which means it's never had a systems solution.

01
It lives entirely in your head
There's no external system for "the excursion form is due Thursday" or "book the dentist before school holidays." It sits in your working memory, crowding out everything else.
02
It doesn't adapt to capacity
Generic productivity systems assume consistent bandwidth. Real family life doesn't. Illness, hormonal cycles, heavy work weeks — the system needs to step back when you need it to, not push harder.
03
The cost is invisible too
When this load is unmanaged, it doesn't just cause missed appointments. It causes decision fatigue, emotional depletion, and the slow erosion of presence in the moments that matter.
How It Works

Five layers. One system.

Home OS runs as a layered architecture — each layer handling a distinct function, all governed by a real-time capacity overlay that adjusts what surfaces based on how you're doing today.

Layer 01
Input + Capture
All incoming information lands in one place — not scattered across inboxes, memory, and sticky notes.
▼
School emails, appointment reminders, renewal notices, and household tasks all route to a single capture point. Nothing requires a decision at the point of arrival.
Gmail filtersLabel routingSingle capture inbox
Layer 02
Triage + Decision
Every item is assessed against the 5D framework — Do, Defer, Delegate, Delete, or Automate.
▼
The 5D framework removes the "what do I do with this?" decision fatigue. Each item has a clear destination. Capacity mode adjusts the threshold — on low days, only urgent items surface at all.
5D FrameworkCapacity-gated surfacingDecision routing
Layer 03
Schedule + Execute
Approved tasks land on a calendar. Recurring ops are wired as automations — set once, invisible forever.
▼
Google Calendar as the single source of truth. Recurring tasks — bill payments, script reminders, uniform cycles — are automated. Deferred items land as calendar events with specific dates attached.
Google CalendarRecurring automationsDeferred queue
Layer 04
Capacity Overlay
A 30-second daily check-in sets the mode. The system adjusts everything else around it.
▼
High / Mid / Low — three modes that gate what gets surfaced, held, or runs on auto. Cycle awareness, transition days, and high-demand periods are built-in modifiers, not afterthoughts. This is the keystone layer.
Daily check-inAdaptive surfacingCycle awareness
Layer 05
Weekly Reset
A 15-minute Sunday ritual surfaces deferred items, clears the queue, and improves the system.
▼
The system learns from each week. What got deferred that needs a date? What automation can eliminate next week's friction? The reset isn't admin — it's the upgrade cycle that keeps the OS improving.
Deferred queue reviewAutomation auditSystem improvement
The Agents

Four domains. One governor.

Each domain of invisible admin runs as a distinct agent — autonomous, focused, and all governed by a shared capacity layer that overrides them when needed.

Agent 01 — School Domain
School Ops Steward
Events, forms, uniform cycles, excursions, pick-up logistics, and school communications — managed as a system rather than a pile of emails and best-guesses.
EventsForms + DeadlinesUniform CyclesLogistics
Agent 02 — Health Domain
Health Continuity Agent
Appointments, script repeats, referrals, follow-ups, and insurance claims tracked across all family members — with 7-day warnings built in so nothing lapses.
AppointmentsScripts + ReferralsClaimsQuarterly Audit
Agent 03 — Household Domain
Household Ops Engine
Bills, grocery cycles, maintenance scheduling, and recurring purchases — automated wherever possible, surfaced with 3-day buffers where human action is needed.
Bills + Auto-payGrocery CyclesMaintenanceRecurring Ops
Agent 04 — Life Admin Domain
Life Admin Warden
Insurance renewals, government deadlines, subscriptions, and registrations — the long-tail irregular stuff that falls through every gap. Runs a quarterly audit to catch anything about to lapse.
RenewalsGovt DeadlinesSubscriptions30-day Warnings
Agent 05 — Cross-Domain Override
The Capacity Governor
The override layer across all four agents. Set your mode each day — High, Mid, or Low — and every agent adjusts what it surfaces, holds, or runs quietly in the background. PMDD cycle awareness and transition day flags are built-in, not bolted on. This is the keystone that makes the whole system adaptive rather than rigid.
Daily Check-inAdaptive SurfacingCycle AwarenessTransition Day LogicCross-Agent Override
The Framework

Every item gets one answer.

The 5D decision framework is the triage logic running under the entire system. It replaces "what do I do with this?" with a clear, fast routing decision for every incoming item.

D
Do
Under 5 minutes, or a hard deadline within 24 hours.
Sign permission slip
Book appointment
Reply to school
D
Defer
Needed, but not urgent. Gets a specific calendar date — not "someday."
Insurance review
Dentist (Q3)
Uniform audit
D
Delegate
You don't need to be the one doing this. Someone else can action it.
Research tasks
Booking calls
Admin follow-ups
D
Delete
Not needed, or the consequence of skipping it is acceptable.
Expired offers
Unused subscriptions
Optional events
D
Automate
Recurring, predictable, low-variability. Wire it once, remove it from your brain.
Bill payments
Script reminders
Morning checklist
Capacity Logic

The system adapts to you.

High
All agents active. Full queue surfaced. All decisions open.
All 4 agents running
Defer queue: visible
New decisions: yes
Mid
Urgent and Do items only. Deferred queue held. No new decisions pushed.
Urgent items only
Defer queue: held
New decisions: no
Low
Automations only. Nothing surfaced. System runs quietly in the background.
Automations only
Nothing surfaced
System: silent
About This Concept

Built from lived experience — not theory.

I'm Zara Grewal — a systems thinker, digital transformation consultant, and mum of two daughters. I've spent 20+ years helping organisations design operational infrastructure that actually works.

Then I looked at my own home and realised: the most complex operation I run has no infrastructure at all.

Home OS started as a personal framework. The more I built it, the more I realised this problem isn't mine alone. It belongs to every parent carrying invisible work they can't see, can't hand off, and can't ever fully finish.

I'm sharing this at an early stage intentionally — because the people who should shape it are the ones living it.

Zara Grewal
Founder, Copper Kettle Consulting · Melbourne
"The problem isn't that parents are disorganised. The problem is that no one built the infrastructure for this work — so it all ends up in one person's head."
— Core design principle
"Capacity isn't fixed. Any system that assumes consistent bandwidth will fail the people who need it most."
— Adaptive design rationale
"The goal isn't to make parents more productive. It's to make the invisible visible — so it can finally be managed."
— Product mission
Early Concept · Seeking Feedback

This is just the beginning.

I'm sharing Home OS with a small circle of people I trust — not to pitch, but to pressure-test. If this resonates, I'd love to hear where it lands for you.

Email Zara Directly