Skip to content
Project Handoff · Internal Canon

Owner's Circle — what is being built, how it operates, and what must not change.

This page is the single source of truth for the developer, Product Manager, Chief of Staff, Finance, and Founder. It summarizes the Founder Vision, the economic model, the governance rules, the current operating model, and the current stage of the program.

The Lovable application is the participant-facing prototype. Real operating decisions — reward proposals, verification, approvals, cash payment, and Owner's Units issuance — are run in the Founder-approved Google Sheet operating workbook during the pilot.

Open Owner's Circle GPT Project Canonical working project space — vision, drafts, and reference materials.
1 · Founder Vision

Reward extraordinary value creation — not job descriptions.

Owner's Circle is Home Alliance's private infrastructure for recognizing leaders who create transformational value beyond their day-to-day role, salary, and standard KPIs. Salary rewards the role. KPIs measure expected performance. Owner's Circle begins where the job description ends.

The program is invitation-only, governed, and long-term. Every reward is tied to a verified, measurable outcome — never to opinion, seniority, or negotiation. The system exists to make participation visible, verified, and permanent.

2 · Economic Model

Verified Value × Approved Rate, split 20% cash and 80% Owner's Units.

Formula
Total Reward = Verified Value × Approved Rate
· 20% paid in Cash
· 80% granted as Owner's Units
· Ratio is fixed. Not negotiable per project.
Example
Verified Value $500,000 × 20% rate = $100,000
→ $20,000 cash paid
→ 80,000 Owner's Units @ $1.00 initial unit value
Owner's Units
Contractual participation units. Not stock, not options, not legal equity. Governed by program documents and award terms. Vest over time. Redeemed in annual redemption windows at the then-current unit value.
Reconciliation
For every issued reward: cash amount + Owner's Units starting value must equal the approved total reward, to the cent. Any deviation blocks payout and redemption.
3 · Governance

Separation of duties. Founder-only high-value approvals. Auditable at every step.

Chief of Staff
Owns program operations. Proposes projects, drafts reward agreements, coordinates verification, prepares Founder approval packets. Cannot approve their own proposals.
Financial Reviewer
Independent CFA-level finance role. Verifies the underlying value figure, the formula, and the calculated cash / unit split. Recommends, does not approve.
Founder
Sole approver of reward issuance, unit valuations, and redemption windows above program-defined thresholds. Immutable audit signature on every approved record.
Council
Consulted on conflicts, recusals, and material program-level changes. Not part of per-reward workflow.
Participants
Accept reward agreements, view their verified rewards, unit balances, vesting, and redemption windows. No self-service adjustments.
Ledger
Every cash payment, unit grant, vesting event, valuation, and redemption is an immutable ledger entry. No stored balances — everything is derived from the ledger.
4 · Operating Model

The Google Sheet is the operating pilot. The app is the vision prototype.

During the pilot, the Founder-approved Google Sheet operating workbook is the system of record for reward proposals, verification, calculation, approval routing, and issuance. The Lovable application preserves the vision, the participant experience, and the reference implementation of the schema and workflow — but is not the transactional system for the pilot.

What the Google Sheet handles
  • · Project baselines and reward agreement drafts
  • · Verified value entry and formula calculation
  • · Financial Reviewer recommendation
  • · Founder approval log
  • · Cash payment tracking
  • · Owner's Units grant register and valuations
What the app preserves
  • · Founder Vision and program narrative (public pages)
  • · Participant view of rewards, units, vesting, redemption
  • · Founder View of the operating sheet
  • · Schema, RLS, and ledger reference implementation
  • · This handoff canon

Reconciliation between the sheet and the app is manual during the pilot. No two-way integration is in scope.

5 · Current Stage

Vision prototype complete. Operating pilot running in Google Sheets.

Complete
  • Public program pages (Home, How It Works, Rewards, Units, Vesting, Redemption, Leaving)
  • Participant reward view
  • Founder View with operating sheet block
  • Ledger, reconciliation, and invariants harness
  • This Project Handoff canon
Frozen (do not extend)
  • New role architecture
  • New dashboards or workflow screens
  • New economic logic or valuation methods
  • Internal marketplaces
  • Additional migrations without Founder + PM approval
Running in the Sheet
  • Reward proposals & agreements
  • Verification and calculation
  • Founder approvals
  • Cash payments
  • Unit grants and valuations
6 · Team Responsibilities

Who owns what during the pilot.

Founder
Owns vision, economic model, all high-value approvals, and any change to the 20/80 split, unit definition, or governance rules.
Chief of Staff
Owns operating cadence, the Google Sheet workbook, program communications, and the handoff between the sheet and the app.
Product Manager
Owns the app roadmap, this handoff canon, and the boundary between prototype and operating system. Reviews any request to unfreeze scope.
Developer
Owns app implementation quality, schema integrity, RLS, ledger invariants, and public page accuracy. Does not add features without PM + Founder sign-off.
Finance (Financial Reviewer)
Owns value verification and calculation checks in the sheet. Signs off recommendations before Founder approval.
Council
Consulted on program-level exceptions and conflicts of interest.
7 · What Must Not Change

Non-negotiables. Any deviation requires Founder approval.

  • The 20% Cash / 80% Owner's Units split.
  • The formula: Total Reward = Verified Value × Approved Rate.
  • Ledger immutability — no updates or deletes to posted entries.
  • Separation of duties between Chief of Staff, Financial Reviewer, and Founder.
  • Founder as sole approver of issuance, valuation, and redemption windows.
  • Owner's Units are contractual participation — not stock, options, or legal equity.
  • Annual redemption windows — not on-demand liquidity, not an internal marketplace.
  • Reconciliation-must-equal-zero before payout or redemption.
8 · Deferred / Out of Scope

Explicitly not in the pilot.

  • Payroll processing.
  • Cap table integration.
  • Tokenization of Owner's Units.
  • External or secondary marketplace.
  • HRIS or generic performance-review tooling.
  • Advanced valuation models beyond the Founder-approved method.
  • New authorization complexity beyond the current role set.
9 · Contacts & Escalation

Where to go with questions.

Program questions
Chief of Staff — for anything about the operating cadence, the Google Sheet, or a specific reward record.
Vision or scope changes
Product Manager first, then Founder. Do not unfreeze scope without both.
Financial verification
Financial Reviewer — for any question about the value figure, formula, or calculation underlying a reward.
App issues
Developer — for bugs, schema, RLS, or ledger questions. Not for economic or governance questions.