An operating environment around the work
City Hall is Aptlantis's project-governance and operational-context system. It connects intent, standards, skills, records, relationships, artifacts, and evidence so human-and-agent development remains understandable across time and handoff. Projects produce the software; City Hall supplies the context surrounding that work.
Where is it?
Identify placement, ownership, and lifecycle state so a project has a discoverable home.
What is it?
Understand purpose, current state, and which records carry authority.
What touches it?
Follow applicable standards, dependencies, decisions, and related artifacts.
The problem: context disappears
A project can keep accumulating code while its intent, rationale, and evidence become harder to recover. City Hall turns that surrounding state into records another person or agent can inspect. The point is fewer mysteries when work resumes.
Intent and decisions are scattered across conversations.
Preserve intent and rationale
Project and decision records keep the purpose, choice, and consequences beside the work.
An agent must infer which rules apply and what it may change.
Make applicability and scope explicit
Name the relevant standards, inputs, constraints, authority, and completion criteria.
A favorable status says little about what was checked.
Connect claims to evidence
Keep artifacts, findings, validation results, and delivery records available for inspection.
The mechanism: standards, skills, and records
These three layers reinforce one another. Standards make expectations explicit. Skills make recurring procedures repeatable. Records preserve what happened and what exists now. Templates and schemas support that structure; they do not replace the judgment behind it.
Standards
Define requirements, vocabulary, applicability, and boundaries. A proposal standard, for example, explains what intent and success criteria must be captured.
Read PPS standardSkills
Package a bounded procedure and its references so a recurring operation can be performed consistently. A skill can also stand alone.
Records
Preserve project state, accepted decisions, exceptions, task outcomes, and evidence beyond the session that created them.
From intent to inspectable evidence
Broad workspace principles become applicable project expectations and observable results. This sequence illustrates the operating loop, not a requirement to apply every standard to every project. Release, maintenance, and preservation each need evidence suited to the work.
Intent
State the problem, purpose, and intended result.
Project record
Capture identity, boundaries, current state, and ownership.
Applicable standards
Identify the requirements that govern this work and why they apply.
Bounded work and skills
Define scope, authority, inputs, outputs, and acceptance criteria.
Artifacts and decisions
Produce the result and preserve the choices made along the way.
Evidence and findings
Record what was checked, what was observed, and what remains missing.
Delivery and continuity
Carry the relevant records into release, maintenance, or preservation.
People set intent. Agents perform bounded work.
City Hall is the environment agents work inside. More context alone does not establish authority, relevance, currency, or permission. Clear task boundaries and inspectable results let people delegate substantial work while keeping consequential decisions visible.
Human responsibility
Set intent, authority, exceptions, and acceptance. Review the result and record accepted decisions.
Agent contribution
Use the current project context and applicable procedures to return artifacts, findings, and evidence within the task boundary.
Read ATS standardDurable handoff
Distinguish proposals from accepted decisions and generated output from verification. Preserve enough context for the next session.
A concrete example: meaning travels with an SVG
The City Hall component logos on this site carry SESM metadata inside each SVG. The artwork identifies a component visually; the embedded record supplies a stable asset identity, semantic description, dimensions, and a public component link. These SVGs contain raster artwork, not vector traces.
Expectation
SESM defines the embedded metadata structure and distinguishes semantic validity from the SVG safe profile.
Read SESM standardArtifact
Open the SESM logo asset and inspect its metadata block to see the structured meaning carried alongside the image.
Inspect SVG asset
Boundary
Metadata is descriptive, untrusted input. It is not permission to act, and its presence alone does not establish SVG safety or an audit.
Take one useful part
The full Aptlantis framework is a reference implementation, not an entry requirement. Start with the recurring problem you need to solve. Combine practices only when their relationships help your work; every adoption level is a valid stopping point.
Preserve project intent
Use a minimal proposal or intake record when goals and boundaries keep getting lost.
Read PPS standardBound an agent task
Write down purpose, scope, constraints, authority, outputs, evidence, and completion criteria.
Read ATS standardInspect delivery
Choose a delivery checklist suited to the artifact and keep missing verification visible.
Explore adoptionVisibility supports judgment
City Hall makes state, requirements, relationships, and exceptions easier to inspect. The effect depends on records being current and practices being applicable. It does not guarantee correctness, universal compliance, or release readiness, and it does not remove human judgment.