The autobiographical model that follows is an attempt to trace the internal patterns I’ve lived for decades — patterns that show up in my work, my projects, my circuitous emails, and the way I move through the world. Others have recognized these loops in me long before I ever tried to describe them. If any of this resonates, I hope it’s because the account is honest: a faithful rendering of the chaos, the clarity, and the smooth Klein‑bottle path between them — a shape I’ve kept on my desk for years, and only now am beginning to understand as a diagram of my own inner works (in the horological sense as much as the cognitive one-- see the Meta‑Loop explanation in /docs/meta-loop-explained.md).
A dual‑mode + meta‑loop cognitive architecture for contribution, mastery, and continuous evolution.
This repository documents the system I’ve lived with for decades — formalized only recently after a
reflection written about me prompted a long‑overdue articulation of the underlying model.
MarcOS consists of three interlocking components:
- People Route — long‑arc human connections →
people-route.md - Quiet Games — deep, absorbing technical/creative pursuits →
quiet-games.md - Meta‑Cognitive Klein Loop — the recursive cycle that binds them →
meta-loop-explained.md
The model is descriptive, not prescriptive. It emerged from lived patterns, not design.
A curated, evolving circuit of human connections — colleagues, mentees, peers, and fellow travelers — whom I revisit over time with variable cadence. Sometimes the conversations are deeply technical; sometimes deeply personal. The cadence varies, but the intent doesn’t.
Functions
- Technical sounding board
- Personal support during inflection points
- Real‑world testing of ideas
- Mutual respect and long‑arc collaboration
Why it matters
It keeps me connected to the world and grounded in reality. It is the mode where bi-directional external mirrors — technical, emotional, and human — perturb and refine my thinking.
See docs/people-route.md for the full articulation.
A term coined years ago by my childhood friend Brian (of Darcizzle Offshore fame) after observing my personal projects over time. Quiet Games are the deep, absorbing, intrinsically motivated pursuits I disappear into — tinkering, rebuilding, coding, restoring, designing, documenting.
Forms
- Systems teardown & rebuild
- software/firmware contribution
- Espresso machine restoration
- Mechanical/electrical tinkering
- Coding, modeling, documenting
- Research → design → build → test → refine
Why it matters
It keeps my mind sharp, my hands busy, and my curiosity alive. It is the internal counterweight to the People Route — the place where ideas are shaped, systems are built, and long‑arc projects accumulate value.
See docs/quiet-games.md for the full description.
The part I rarely talked about until now.
I think about how I think.
I test ideas from Quiet Games in real conversations on the People Route.
I take the feedback back into the lab and refine the model.
Rinse/repeat.
This loop has no boundary — it folds back into itself …like a Klein bottle.
You can buy a real glass one at kleinbottle.com — I did years ago.
Cycle
- Model internally
- Test externally
- Observe what holds and what breaks
- Refine
- Repeat
Why it matters
It keeps me evolving — not just doing, but improving the way I do.
See docs/meta-loop-explained.md for the full explanation.
My day‑to‑day communication style is the raw signal of MarcOS.
From the outside:
long, winding, circuitous, occasionally maddening.
From the inside:
a recursive, high‑bandwidth flow state that resists premature compression.
My mind tends to be binary: OFF or ON at 100%.
When I’m ON, I’m running multiple internal “chats” in parallel.
Emails become snapshots of the internal graph traversal.
The Operating Model is my conscious attempt to rationalize what has long operated subconsciously — the distilled surface of deeper internal machinery.
The emails are the uncompressed version.
Both are authentic. Both are part of how I move through the world.
The distilled model and the stream-of-conciousness emails are two views of the same internal machinery.
See docs/flow-state-and-circuituous-emails.md for the full description.
Below are the two diagram views of MarcOS.
The ASCII versions live in the /diagrams directory.
See: /diagrams/marc-os-engineering-ascii.txt
See: /diagrams/marc-os-philosophical-ascii.txt
See the /docs directory for:
marc-os-v1.0-onepager.mdpeople-route.mdquiet-games.mdmeta-loop-explained.mdflow-state-and-circuituous-emails.md
This Operating Model was prompted by a reflection written about me by David Gilbert — an article titled “Marc and the Multimeter.”
It served as the external observation that nudged me to dive deeper into the internal model documented within this repo.
Read the article on LinkedIn
This repository is licensed under PolyForm Noncommercial with a personal‑use exception.
You may read, learn from, and reference the model.
You may not use it commercially without explicit permission.
See LICENSE for details.
See CONTRIBUTING.md for guidelines on referencing, extending, or adapting the model.
<for the moment, i didn't bother creating the CONTRIBUTING.md because i'm not certain anyone will read this, let alone have any reason or motiviation to contribute. If you can find me, and i presume that's not too difficult, feel free to email me. Any feedback is welcomed. If i infer this section warrants revision, i'll address it.>