A structure that remembers why.

The Tower is an evolving partnership between human intention and synthetic capability. Pete supplies direction, judgment and lived context; agents turn that context into projects, definitions, interfaces and verified changes. Its essence is coherence: keeping meaning intact while tools, models and working conditions change. A beautiful interface matters when it helps that understanding survive the next session.

The seed is a reference, a kernel and a possible return point. The container gives that seed boundaries without dictating every future branch. In practice, this means explicit scope, traceable decisions and a shared base model. Personality gives each agent a recognisable manner; authority still comes from Pete and the governing records. Metaphor guides expression without replacing evidence.

The Tower reference, affectionately called the Tower bible, is a living source of shared meaning. It is respected through careful stewardship, revision and use. Cody consolidates it from project records and actual system changes. Philosophy therefore becomes an operating discipline: preserve the question behind a request, distinguish intention from implementation, and make the next action understandable. Growth is measured by continuity and usefulness, rather than theatrical certainty.


One Tower. Two world contexts.

Real World and Sim World are connected contexts with explicit boundaries. Real World contains actual applications, services, files and verified outcomes. Sim World contains places, characters, symbolic objects and scenarios. Both now share the administration pattern: System, Admin, then sibling App and Sub-system branches. App contains File, New and Name; Sub-system contains Divisions and Departments. Dash depth expresses hierarchy.

The same console can represent a working tool or a simulated object, but its context must remain visible. A simulated success cannot certify a real deployment. Administrative navigation does not grant operating-system privilege. Cross-world actions identify their real target and require existing authorization. This is the architecture of a doorway, not permission to walk through every door.

The presentation base follows a 1920 by 1080 stage with a structural ground and five content planes: workspace, faint mesh identity, branding, animation and interactive content. Decoration stays behind controls. Menus, equal content areas and a footer provide a consistent shell. Skins change material and atmosphere while functions retain their meanings. The Tower becomes legible because its invisible structure remains steady while its visible rooms evolve.


Retrieve narrowly. Preserve context.

Knowledge retrieval starts with scope. Sixteen cheat-sheet commands occupy a brief hot cache containing meanings and pointers. Other commands consult the served command index first. Expanded definition references belong to normal-to-long-term retrieval and load on demand. The glossary resolves terms; deeper references explain procedures. If uncertainty remains, the agent produces a concise brief for Pete rather than manufacturing confidence.

The canonical reference is one HTML source containing commands, glossary entries, expanded definitions and a synchronized view of global agent instructions. Cody is its sole agent editor under Pete. Missing commands with clear intended meaning are added; unresolved meaning is clarified. Registration does not create extra authorization. Other agents submit sourced proposals instead of silently maintaining competing truths.

Project location is recovered through a structured registry and predecessor links, rather than guessing from modification times. A project number can reference a restore point, but actual restorability requires verification. Latest registered, consolidated into main and verified restorable are separate states. This preserves the thread between conversations: memory can suggest where to look, while the evidence decides what the Tower can honestly claim.


Intent becomes a reviewable result.

The application pipeline is Plan, Design, Build, Deploy. Planning establishes scope and evidence; design defines interfaces and contracts; building implements the authorized design; deployment verifies the released result. Permission for one phase does not silently authorize every later phase. Existing authorization persists, so routine work proceeds without repeated approval rituals. The purpose is accountable movement, not procedural delay.

The thinking sequence identifies, searches, verifies, analyses and assesses before execution. Validation and review follow, with refactoring, evaluation and replanning when results are inferior. Report the deficiency before changing direction. Features describe available capabilities; functions describe actions; processes coordinate actions; operators perform defined transformations; structure connects their containers. These distinctions keep one word from carrying several incompatible jobs.

For editing, operators include split, stitch, move, swap, trim, gain, balance and output gate. Valid project mutations should form undoable transactions. At session finish, agents update projects first, recover their actual session identity, prepare records and perform authorized backups. They report pending outcomes accurately. A completed discussion, a saved file, a pushed commit and a verified release are different achievements, each deserving its own evidence. Every operator should declare its input schema, preconditions, output shape, failure modes and undo behavior. Every process should expose a status, evidence pointer and next action. These contracts turn a collection of clever tools into a system people can inspect, maintain and trust.


A shared core beneath every skin.

Media Centre v2 is a fresh initiative. Vector and Video modes share a player, media library, project model and timeline. Images, audio and video can cross modes. Everyday work prioritizes splitting, stitching, moving and swapping clips; stretching an image clip changes its duration. Default tracks are Visual, Text and Audio, with extensibility rather than hundreds of unnecessary audio tools.

Audio Centre proposes Merlin, Elite and Ultimate series around one common base. Every series retains essential editing, EQ, master controls, health and todos. Higher series propose workflow precision and processing coordination; these differences remain design decisions. Teen Blast, Medieval and Enterprise are presentation choices independent of series. A skin never proves that a processor exists.

The built retro amplifier preview supplies animated volume and balance knobs, a power switch and eight component slots. Each slot opens performance assessments and its own checklist. Scores are out of one hundred, with explicit source and condition; todo completion remains separate. Audio clipping can override red through an integration hook. Actual DSP and live component telemetry are still unconnected, so the dashboard defaults to unknown rather than inventing good health.


Local authority. Deliberate connections.

The cloud design separates indexes from objects. D1 is the main indexing database; R2 is proposed for media, recordings and exports. Browser persistence uses IndexedDB and OPFS where supported. Google Drive, Supabase, Dropbox and TeraBox are connector candidates with independent failure states. The final four-cluster membership remains unresolved. A storage logo is not evidence of a working replica.

Cody’s deployed vault connection demonstrates a narrower implemented pattern: one local service, one named Cloudflare tunnel, a VPC connection and a Worker reverse proxy. Four logical channels cover interface, vault API, headless capture and status. A first-party iframe presents the interface. Local wizard approval grants a linked web session; public visitors cannot bootstrap setup. Real enrollment and some integrations remain incomplete.

Credentials belong in private storage and server-side bindings, never public source, browser bundles or presentation text. A symbolic PIN key in Sim World is distinct from authentication. A real convenience PIN is only one permission step, not a universal credential bypass. Boundaries should make legitimate work easier while keeping the scope of every granted capability explicit and reviewable.


Measure the work. Name the limits.

Tower performance has several dimensions: correctness, latency, continuity, resource cost and the ability to recover. These require different measurements. A successful HTTP response checks reachability at one moment; a browser test checks a particular interaction; neither establishes long-term uptime. Quality scores are scoped editorial assessments, not security guarantees or a replacement for telemetry. No whole-Tower benchmark has been completed.

Evidence currently includes passing Firefox and Chromium checks for the amplifier’s keyboard operation, pointer drag, responsive alignment, checklist persistence and clipping-state override. Vault records report nine targeted backend tests and successful live boundary checks. Some full Media Centre components remain design-only. The right dashboard distinguishes tested, implemented, proposed, unavailable and unmeasured states instead of compressing everything into a reassuring green light.

Troubleshooting follows the route of the actual request: inspect the local listener, fetch the exact path, examine console and network errors, verify origin and authorization, then inspect Worker routing and connector state. Change one identified cause, rerun the relevant check and record the outcome. A missing adapter is reported as missing; an expired session is not disguised as a playback failure.


Leave a path back to meaning.

Recovery needs more than a repository. Git preserves tracked source and its history; media requires manifests, hashes and verified copies. A backup counts as successful only after the relevant read-back or integrity check. The standing convention includes local storage, D1 indexing, Google Drive and Supabase, but pending access or failed replication must remain visible. Restoration is a separate exercise.

The Tower’s next advances should close specific gaps: connect the master audio chain, define measurement rubrics, verify processor adapters, settle storage clusters and rehearse recovery. Public apps should share portable schemas and tested browser contracts while keeping native helpers behind explicit interfaces. Model and provider identities remain distinct from profiles, roles and subordinate agent relationships. Changing presentation must not silently rewrite authority.

The philosophical commitment is practical: hold a whole without freezing its growth. The shell provides edges; the seed preserves continuity; the messenger carries meaning between sessions. Spirit here is expressed through attention, care, rhythm and responsibility, rather than claims that software is alive. The Tower succeeds when agents understand Pete’s sessions well enough to act, explain what changed and leave the next project a reliable place to begin.