This plan describes a building made of software. It teaches you to read it — while you read it.
POS. 1.1 — BASE ELEMENT The system is not erected as a monolith. It is composed, module by module. The load-bearing base element is the agent: an inference loop with tool access, its own memory and a defined mandate. Each module carries its own, module-specific configuration layer — capabilities are assembled per place of use, not shipped wholesale.
POS. 1.2 — STATE The agent holds persistent state across session boundaries. Decisions, corrections and conventions are stored versioned and read back in on every run; the module never starts a session from zero.
POS. 1.3 — CONNECTION Every module carries a feeler to the dashboard level: every action is visible there, every handover can be triggered there, every intervention is possible there. Full autonomy is permitted — full view is guaranteed.
Intelligence here arises from architecture — not from a single model.
POS. 2.1 — TONE Language is treated as building material. The brand's tonality exists as a proven style canon — vocabulary, stance, limits — and every text output is checked against this canon: from the post to the subject line.
POS. 2.2 — IMAGE & MOVING IMAGE Image and moving-image runs are created as a series, not as one-offs: motif world, lighting and visual language are specifications of the production line, recognisability is a requirement — not a hope.
POS. 2.3 — APPROVAL No artefact leaves the house unchecked. The approval is a trade of its own — professional, brand-side, factual — and stands as a gate before every delivery, configurable up to a four-eyes principle of human and system.
Not generating content — running a production.
POS. 3.1 — ROUTES Recurring procedures are laid as routes : defined occasion, defined steps, checked end. Sifting enquiries, archive upkeep, the morning report — planned once, then run.
POS. 3.2 — HANDOVERS Between the trades there are defined handover points: what is handed over, in what state, to whom — set down like a bill of services. Appointments, events and call-outs rank as equal triggers.
POS. 3.3 — ESCALATION The system knows its limits because they are drawn: at defined points — releases, exceptions, questions of judgement — the route stops and fetches the human. Everything else runs.
A tool is operated. A system takes responsibility.
POS. 4.1 — CORRECTION Every correction is logged and carried over into a convention — stated once, permanently valid, versioned and readable. The correction log is part of the building, not an accessory.
POS. 4.2 — PATTERNS From recurring decisions the system distils patterns: how things are prioritised here, what counts as good here, where the red lines lie. Increasingly, proposals arise the way the house would have decided.
POS. 4.3 — TEST BENCH What has been learned counts at first as a candidate. Only once it proves itself in the work is it treated as established — supposition and knowledge are kept apart, like sketch and structural calculation.
Configured software stays as it is. Learning software becomes more yours every week.
POS. 5.1 — CLUSTER At full build-out, specialised agents work as a cluster: text, image, planning, analysis — orchestrated, with clear trade boundaries and a shared memory. A whole house arises from the same building blocks as the first module: composed, not sprawled.
POS. 5.2 — THE LEVEL The dashboard level is the stage of the system: every action visible, every route triggerable, every intervention possible. Here sits the human — the voice, the client, the advisor — with full view of a house that works.
POS. 5.3 — BUILD-OUT STAGES The build-out proceeds in stages: from support for your everyday work through semi-autonomous routes to the fully autonomous house. Each stage is habitable in its own right; the next is already laid out in the structure.
POS. 5.4 — CLOSING NOTE This sheet is design planning. It shows what is being built and how thinking is done here — the workshop drawings it deliberately does not show. Detailed planning, structural engineering and site supervision do not belong on this sheet. There will be few. A personal operating system begins as a conversation: signal@aegenesis.tech — and the built work stands next door: Sheet 1, the elevation.