How Alexandria works

This is Alexandria, described in Alexandria.

One living model, written mostly by agents and read by people.

Every view is generated from it.

The twin

Five kinds of things make the twin.

Use cases, parts, data, flows and where it runs.

Here they are for Alexandria itself.

Write

An agent adds a use case.

Alexandria’s agent records “Compare two drafts”.

It is in the twin at once, for everyone.

Look · Use cases

Who needs what?

Every use case has someone who needs it.

Your agent, a person, the team, leadership.

Look · Domain

What are the concepts?

A project holds drafts. A settled draft becomes a revision.

Scenarios run through drafts; decisions settle them.

Look · Map

How does it work?

Pick “Compare two drafts”.

The map traces it through Alexandria’s parts.

Look · every view

Eight views, one question each.

Flows, data, deployment, forecast and the logbook read the same twin.

Nobody draws, so the views never disagree.

Try

Try a variant as a draft.

Draft B splits reading and writing.

The same scenario runs through both, side by side.

Settle

Settle it in the logbook.

The decision is recorded with its reason.

Readiness rises for everyone to see.

Two lenses, one twin

Everyone reads the same twin.

Product sees use cases, engineering the map and forecast, leadership readiness.

The agent reads the same items as structured context.

Next and later

A settled twin produces, then follows the system.

Next: Terraform, SQL schemas, prompts, benchmarks, tasks and documents.

Later: live load on Alexandria’s own map.

Alexandria’s own model, as an illustration. Next and later are direction, not yet built.