Felt Faction as a Company with a Shared Brain

Idea Search related

Brainstorm — captured 2026-07-05, treatment as venture.

Connor thought commercialising Felt Faction would be worthwhile. Nathan's parallel instinct: a Felt Faction venture would benefit from an autonomous company brain that runs parallel to his personal gbrain, with the two sharing an underlying knowledge layer.

This is the literal YC Request for Startups company-brain category.

Shared brain name: brain-shared (CORRECTED 2026-07-05)

Initial instinct was to call it "felt-faction" — user pushed back: the scope isn't just Felt Faction, it's whatever Nathan + Connor share. A venture is one possibility; the joint life is broader. The brain is named after the relationship, not the venture.

FieldValue
Source idbrain-shared
Name"Shared (Nathan + Connor)"
Path/Users/nathanmaxwell/brain-shared/
Federatedyes (appears in Nathan's cross-source search)
Layoutshared/ + nathan/ + connor/
ModelB (one source, per-person folders, agent-enforced boundary)

Felt Faction may be in here, but so might:

Geographic anchor (CORRECTED 2026-07-05, x3)

Both co-facilitators are Sunshine Coast QLD locals — Nathan since late 2012 (school + immediate family), Connor since 2020 (school + immediate family).

The prior recall framing of Felt Faction as Canberra-anchored was wrong three times over:

  1. First wrong: "Canberra area" as a home-base signal. The brain

had Nathan + Connor anchored to Belconnen/Canberra. SC has been home since 2012 / 2020. (The Chingaari dinner was on the SC, not in Belconnen — see second correction below.)

  1. Second wrong (homonym collision + venue mix-up): "Carwoola"

in the Felt Faction ledger is Carwoola Crescent, a residential street in Mooloolaba, Sunshine Coast — not the rural locality called Carwoola near Queanbeyan / Captains Flat in NSW. And the 2026-07-01 dinner was at Chingaari Indian Restaurant, 3/61 Burnett St, Buderim QLD 4556 (Sunshine Coast) — not at a "Chingari's in Belconnen." Two errors that both looked like Canberra references but were both Sunshine Coast references the LLM pattern-matched sideways. The brain had it wrong twice; two user corrections in a row caught it. Verified via web search 2026-07-05: Carwoola Residence by Reitsma, Mooloolaba on the Sunshine Coast; Chingaari Indian Restaurant, Burnett St, Buderim QLD 4556 (Instagram + EatClub + Uber Eats).

  1. Third wrong (theory was wrong, not just the example): The

prior two corrections hypothesised the drift was driven by a "recent Canberra touchpoint" — citing "UniSC term" as one such touchpoint. That theory was itself wrong: UniSC = University of the Sunshine Coast, Sippy Downs QLD (formerly USC until the 2022 rename). It is not a Canberra institution and has never been. There was no "Canberra touchpoint" — the SC correction should have stopped at "the LLM pattern-matched sideways on a SC context and anchored it to Canberra because that's what the brain's recall bias defaulted to." Lesson: the LLM drifts to Canberra by default on QLD/NSW place-names regardless of what the actual context is. The fix isn't "find the recent touchpoint" — it's "verify the location every time, regardless of context." See skill place-name-verification for the full recipe.

Consequence: "Carwoola Credits" is geographically correct as-is. The ledger already points home. The "rename to Coast Credits?" question from the prior correction is moot. Whoever named it picked a street near the co-facilitators; that's a deliberate brand call, not an accident.

Consequence 2: SEQ is unambiguously the home market for the venture. Co-location is the strongest single signal for viability:

geographically unambiguous

thing, the LLM just drifted the framing

The two-thread structure

  1. The product/venture: commercialise Felt Faction. What does

that mean — sell a service? license the format? build a SaaS that lets other groups run their own Felt Faction? Membership model? Open until scoped.

  1. The operating system: the shared brain itself

(brain-shared) runs on gbrain — separate source from Nathan's personal home, federated, with Nathan + Connor each getting scoped access via per-person folders. Per-person crons. The gbrain repo literally ships a tutorial for this (docs/tutorials/company-brain.md).

These are entangled: the shared brain is the operating system of the joint life. The venture's product and the venture's ops are the same artifact.

Why this isn't speculative

exact setup: federated sources, per-person folders, OAuth scoping, HTTP MCP, per-person crons

this is a sanctioned direction, not a fringe one

the prerequisite is in place

committed to following Nathan to Europe, peer/co-facilitator on Felt Faction) maps cleanly to "co-founder of a venture that has a brain"

distance. The venture's founding ops are inherently local (casino nights, ledger reconciliation in person, member vetting over coffee). SEQ is the test bed.

identity doesn't need to be re-built from a Canberra placeholder; it was never that.

up. Source registered (brain-shared), scaffold committed (shared/ + nathan/ + connor/ folders, README + HOW-WE-WORK pages), first sync ran clean, shared/how-we-work page indexed with full embeddings in the gbrain DB.

What to scope in this brainstorm

The venture shape (open)

sold/licensed to other groups), the vehicle (a service business Nathan + Connor run themselves), or both?

Brisbane)? AU? AU + EU (post-2028 move)? EU-first given Connor's Italy preference + Munich luxury automotive cluster?

Licensing the Carwoola Credits (CC) ledger to other social clubs?

The brain shape (clear from the repo, now also live)

brain-shared (the joint life), with brain-shared having per-person folders (shared/ + nathan/ + connor/) inside it

is a separate source, federated-read across the two

member churn, ledger audit, season summary, etc.

season-close, member-vetting, cc-ledger-audit, casino-night-run-sheet

(per the tutorial's 25-person cost basis — we'll be well under)

The decision to make first

The repo tutorial assumes one of two scoping models:

different AI clients. Right shape if Connor runs his own client (Claude Code, Cursor, his own Hermes).

when ONE agent (Nathan's) serves everyone. Right shape if the shared brain is really just Nathan's agent with a Connor-facing scope.

For a 2-person shared brain, Model B is almost certainly correct to start (and is what's actually wired up today). Add Model A later if Connor spins up his own client.

The interesting framing (saving as a principle)

The Felt Faction brainstorm reveals something generalisable:

A personal gbrain is a single-player RPG. A shared gbrain is a multiplayer RPG with shared loot, scoped inventories, and party roles.

The "shared brain" metaphor is doing real work here:

membership roster, the joint 2028 EU plan) — anyone in the shared brain reads + writes

Connor's marketing outreach) — only that person reads + writes

Felt Faction project page, his thoughts on social-club mechanics) — they migrate into the shared brain but stay Nathan-private until he chooses to share

members rotate, when seasons end, when Nathan + Connor are both in different cities in 2028+, the brain is what remembers the rules, the ledger, the seasons, the wins

The personal gbrain is personal. The shared brain is the shared life. They share a substrate but not a permission model.

See also

thesis + EU move commitment; SC local since 2020

the artefact being commercialised; Carwoola Cres = Mooloolaba, not Canberra

career direction (luxury / sports, not pure EV)

the shared brain's longer-term geography (Munich lead)

category sponsor

the personal gbrain the shared brain extends

conventions page

Open

appetite for a venture is unknown until that lands. (The v10 message is about the 2028 EU move, not about commercialising Felt Faction; the venture pitch needs a separate thread with Connor.)

"Carwoola Credits" canonicalisation, since it's the joint artefact the two of them have already built. Pending Connor's appetite.

decision before more brain shape gets locked

pages (in projects/felt-faction, the v1-v10 brainstorm lineage, the CC ledger notes) move into the shared source? What stays personal?

isn't fully solved by the repo's current tutorial — that's a gap worth documenting if we end up implementing it