This morning's strategy session happened on a walk in the Wissahickon, out loud, into my phone. By the time I was back at my desk the voice memo was a memory in my company's perspective: the decision I had talked myself into, attributed to me, dated, sitting next to the two earlier claims it revised. That afternoon the coding agents building our product were already working from it. Nobody briefed them. They ground themselves in the perspective before they write, and the perspective had moved.
Aswritten is a company of one human, and it does not run on my memory. It runs on its record.1 Call transcripts and voice memos are the two inputs; everything I decide out loud lands in a versioned graph of claims with conviction levels, and everything the company produces compiles back out of it.2 The investor brief on our site was written from the perspective and cites it. The landing page was. The grant application I submitted this week says so in its method note: nearly every sentence is something I said on a walk, on a call, or in an essay draft, and the footnotes were generated by running the draft through our own citation tool. The application is a demo.3
The part I did not expect is what this does to the idea of a team. The roles I cannot hire yet exist anyway, as perspectives contributed to on a cadence: the advisor who thinks about sales lives in the graph through every call we have recorded, and the AI that drafts outreach with me draws on his actual objections, cited, instead of my paraphrase of them.4 A collaborator building agent-orchestration systems and I found the boundary between our companies in one sentence: he builds the loop, we are the memory the loop runs on.5 An entrepreneur running agents without a memory is re-explaining the company to their own tools every morning.6
I still make every call. The perspective does not decide; it remembers what I decided, in my words, and holds my agents to it. When I change my mind the old position stays in the record under the new one, which means my company's history of thought is versioned like its code, reviewable like its code, and steadily becoming the most valuable thing it owns.7 The org chart of a one-person company turns out to be a perspective. This article came out of it too, citations below.
In the June 12, 2026 process redesign session, Scarlet Dame finalized the transition to running the company entirely on its own repository-native record:
"Notion was abandoned in practice but not formally retired. The June 2026 session made the retirement explicit."
The decision marks the first Organization-domain memory in the graph: company operations run on versioned files rather than external SaaS tools, down to the CRM itself, which migrates into the repository to eliminate the last outside dependency.
The product architecture anchors the company in a unified, compile-ready semantic layer:
"Same graph, same ontology, same SPARQL transactions. Same compile, same introspect. Same memory format, same ingestion pipeline."
Everything the company produces compiles back out of a single versioned graph of claims, and the adjacent principle from the March 2026 architecture review completes it: every Aswritten repo IS a perspective. The code and the worldview are structurally one.
In a July 2, 2026 drafting session, Scarlet Dame formulated the promise that drives the company's own public assets:
"aswritten enables AI to be highly opinionated in a particular direction, citing the conversations that opinion comes from, and getting more opinionated over time."
The positioning turns the company's landing pages and applications into live demos of the product. The citations are what make the promise safe and sellable: the why is receipts. And the adjacent insight closes the loop across hiring, funding, and buying: an application or landing page arguing this demonstrates itself.
A May 19, 2026 vision session surfaced that the bottleneck in scaling a team is scarce memory at decision junctions, structural to the role rather than personal:
"The forgetting bottleneck is structural to the decision-junction role, not personal to any individual — two independent self-diagnoses from different roles confirm the pattern"
The same principle lets external roles live continuously in the graph through recorded calls, extending the March 30, 2026 claim that organizational roles can be represented as perspectives contributed to on cadence rather than as full-time hires.
In the May 26, 2026 organizing session, Scarlet Dame drew a sharp boundary between execution loops and memory systems:
"In every use case, aswritten is the memory the steering runs on — read at the start of the work, written at the end — never the tool that does the governing or orchestrating."
The principle hardened into a positioning constraint: Aswritten is substrate. The orchestration loops belong to collaborators and agents; the durable memory they run on is the product.
In a June 30, 2026 discussion, Scarlet Dame named the friction of running agents without a persistent, conversationally grounded memory:
"we're either constantly re-explaining ourselves, or we're creating these really highly bastardized, summarized, never-current product or engineering architecture documents and saying please read this — which is really just RAG, and you're missing the conversational why behind it."
A design advisor's independent finding validates the point from the other direction: AI-applied surfaces break entirely without a persistent, tokenized lens. A structured perspective is the part of agentic work that cannot be commoditized.
In a July 3, 2026 developer-tooling review, Scarlet Dame connected the company's own engineering constraints to the product thesis:
"Because you cannot hand off through shared model cache, the durable handoff medium becomes written, cited context — the spec, the perspective, git. That is aswritten's own thesis: durable perspective is the memory substrate that agents run on, never the loop itself."
The company's history of thought is versioned, reviewable, and durable like code, extended by the decision to route all model handoffs through written artifacts in git rather than volatile session caches.