Aswritten.ai

02 · connect

you

We’re six people on twenty client calls a week — Zoom outside, Teams inside, Fireflies on the rest. Connect them.

Connect once. Calls import as they end.

a teammate · thursday

what changed this week? I was out.

Your calls become the perspective. Your team reads the change.

03 · introspection

I'm thinking about repositioning the demo around agent deployment. It feels like something's missing.

Here's what's there, and here's what's thin:

Agent deployment is your use case 2 — and it's currently underrepresented: the steering-loop frame is settled, but almost nothing witnessed shows an agent running on it.

The "opinionated promise" argument is missing — you've named it, but it isn't written anywhere yet.

Introspect spreads the graph apart — the gap is visible.

go deeper all →

1

Case Study: Writing Discovery Docs with Conversational Provenance

Two weeks of stakeholder interviews, one report the client will actually trust: every finding cited to who said it, dissent preserved, and the perspective stays queryable after the consultants leave.

2

Unidentified: Individuality in the age of AI

The TSA scanner flags my trans body as an anomaly. What a system trained on centralized norms does with difference, and where the ownership of digital individuality will lie.

04 · remember

▸ voice memo · 22:58 · Saturday morning walk

Here's my memo on the landing page — the scroll experience idea.

This changes the landing-page position: the scroll-experience direction supersedes the deep-link hero action — the prior decision stays in the graph, with lineage.

One of yesterday's gaps just got thinner.

expressions "the page is really text-heavy…" "…a true curated scroll-driven animation"

position The page should perform the product, not describe it show-don't-telldecision

narrativeNarrative_ScrollDrivenLandingPage

TX 2026-07-04 landing-scroll-vision.sparql → committed · pushed to your GitHub

Speech becomes statements. Statements become the graph.

go deeper all →

1

Case Study: A Company of One Human

A founder's working day, followed from a voice memo on a walk to the coding agents that obey it by afternoon. The org chart of a one-person company turns out to be a perspective.

2

The Anatomy of Aswritten

The structure behind the landing page claims. A graph of who said what, a memory you approved as the only thing that crosses, and the verbatim quotes that make every citation checkable.

05 · review

a teammate · next morning

how did the team's thinking change this week?

One change is waiting on your review:

memory/landing-scroll-vision → main Landing page: scroll experience supersedes deep-link hero 1 memory · 1 transaction · supersedes 1 decision · awaiting review

review it — show me what it does to what I'm working on, not just the triples.

It touches the landing page hero. Projected both ways — better through A, or through B?

A · as it reads today content/landing.md · hero

Turn transcripts into perspective. "The voice memo from my walk in the woods laying out the fundraising plan… cited by AI, aswritten."

B · with this memory applied projected — not yet written

A question is already typed when you land. Scroll, and the answer is built in front of you. The page doesn't describe the product; it performs it.

✓ approve & merge

Review is an optometrist visit — better through A, or B?

go deeper all →

1

Case Study: AI Engineering Governance Through Extracted Human Call Transcripts

The architect whose brain the company joked about duplicating, the review board whose decisions evaporated, and the pilot that turned six months of transcripts into the record steering the team's AIs.

2

Artifact: A check-in to a customer, with the numbers behind it

A short note from Scarlet, paired with the data showing why she's writing.

06 · share

you

Create a share from client/acme-discovery — it's the repositioning work for Dana. She should see it evolve as we go.

Don't send a deck. Send the perspective.

— elsewhere, Dana signs in —

dana · acme

load perspective share ID acme-reposition-dana-7f3e

Imported. This is the repositioning perspective prepared for Acme: 34 positions, the pricing rationale with its decision lineage, and two questions flagged open for you specifically.

go deeper all →

1

Case Study: Delivering a Perspective Instead of a Deck

The practitioner whose craft never survived the handoff: what happens when the deliverable is the way of thinking itself, installed into the client's AI, cited by name, escalating back to its owner.

2

Artifact: A legal cover note, made readable

An MSA and SOW delivered with the rationale alongside — what was negotiated, why, and what's binding when.

07 · deploy

Ravenline wants to vet us before they sign — give their team an agent that answers from our perspective. Text and Slack.

Deployed. Their team can text the number or ask in #ask-aswritten — every answer carries its citation, and you hold the thread from the field inbox below.

21:42▪▪▪

quick one before this call — what do we actually mean by “perspective, not information”?

“We're not just loading a set of information; we're loading a set of perspectives, narratives, approaches, processes, and opinions about how that information is used, framed, what it means.”^†

† verbatim — Obs_PerspectiveVsInfoQuote

acme co # ask-aswritten

# ask-aswritten

jordan is the SMS number the product? trying to write the one-pager

aswritten No — the channel is distribution, not identity. The product is expertise installation; SMS is one place it answers from. ↩ Narrative_ChannelIsDistributionNotIdentity

aswritten · field inbox

+1 ···· 4471 sms what do we actually mean by “persp… 21:42 · auto-answered

jordan slack is the SMS number the product? tryi… 21:38 · auto-answered

+1 ···· 4471 · 21:42

quick one before this call — what do we actually mean by “perspective, not information”?

aswritten agent · auto · 9s

“We're not just loading a set of information; we're loading a set of perspectives, narratives, approaches, processes, and opinions…”

perspective context — not sent

Matched the core differentiator cluster. Chose the verbatim witness over a paraphrase — caller is mid-sales-call, the exact words carry the conviction.

Obs_PerspectiveVsInfoQuote · decision-level Narrative_PerspectiveVsInformation · extends Claim_CategoryDefinitionCuratedExpertise · adjacent — withheld, too much for SMS

go deeper all →

1

Case Study: Transparent Agents

An agent that never asks to be trusted: every claim carries who decided and when, and when a question reaches past the record it escalates, naming what it was missing.

2

Artifact: A parallel architecture, written between two founders

Briefing for an agent-systems builder. The reframe: their project builds the loop. aswritten is the memory the loop runs on.

08 · white space

Draft the Acme pilot proposal. Keep it to a page.

Here's the one-pager. Nine words in — every section below came from a decision you already made:

Scope follows the ARB-replacement pilot pattern — the shape that worked in the last engagement.¹

The price is the pilot number you set in February — carried in, not guessed.²

Security is zero data retention by architecture, exactly as negotiated in the March MSA.³

And it reads in your voice — plain language, no jargon, per your editorial rules.⁴

1

ARB as the pilot use case: replace the architecture review board.

Narrative_ARBPilotUseCase · decision

2

Pilot pricing set in the February plan — extraction plus the working perspective.

ConsultingEngagement · decision

3

ZDR by architecture, not by policy promise.

SecurityPrivacyModel · decision

4

Plain language; the jargon stays out.

PlainLanguage · principle

2 pages · 14 decisions applied · 0 invented facts.

The draft fills in the thinking the organization already did.

go deeper all →

1

Case Study: Onboarding Human and AI Employees

"People have no fucking clue what to do when they join a company." Your AI is a new hire you re-onboard every session. One perspective onboards both kinds of employee.

2

Artifact: Pilot week one — the adoption snapshot

Active roster, tool mix, what's working and what to watch for — from the live telemetry of a 17-person enterprise team after seven days.

09 · custody

Wait — where does all of this actually live?

In your GitHub. Every conversation, every transaction, every digest — plain files in a repository you own. Leave, and you take all of it with you; nothing is held hostage in someone else's database.

Zero data retention by architecture, not by policy promise — the model providers never store your content.

their compliance lead · inevitably

And the call recordings themselves? GDPR, data sovereignty — this is exactly where vendors fail our review.

go deeper all →

1

Technical White Paper

Narrative architecture: the 15-year thesis, the shipped system, its honest limits, and where it is headed. Fully cited.

That wasn't a mockup.