ASWRITTEN[AI] try it live →
click to edit · ↵ asks the live public perspective
connect your own AI →
loading the perspective…
AI that answers from your own conversations. Receipts included.

go deeper all →

Scroll to watch it answer. or type your own question
02 · 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.

03 · 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.

"the page is really text-heavy…" "…a true curated scroll-driven animation"
The page should perform the product, not describe it show-don't-telldecision
TX 2026-07-04 landing-scroll-vision.sparql → committed · pushed to your GitHub
Speech becomes statements. Statements become the graph.
04 · review
T 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
05 · share
you
Create a share from client/acme-discovery — it's the repositioning work for Dana. She should see it evolve as we go.
— elsewhere, Dana signs in —
D 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.

06 · 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
07 · 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.1

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

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

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

1
ARB as the pilot use case: replace the architecture review board.
Narrative_EscherARBPilotUseCase · 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.

08 · 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.

That wasn't a mockup.

Every conversation you just watched flow in is real — the actual recorded history of this company, public at github.com/Aswritten-ai/perspective. The answer, the citations, the graph: that's the product answering questions about itself.

Install a perspective into your AI or schedule a call with Scarlet →

Not ready yet? The perspective keeps writing.

Check your inbox — one click to confirm. That didn't send — try again?