The question a client conversation actually turns on is not whether something is built, but whether it survives being opened without you in the room. Three answers, and only the first is a link you can send and walk away from.
The strategy, the science and the tools, written to be read start to finish by someone who has never heard of us.
/pollicaThe week itself: photographs from the boat and the classroom, each tied to the tool it produced.
/pollica/storyThe coast as a grid of meadow density and per-zone stress. Opens with the coast already loaded.
/pollica/demoPull the levers a town actually holds and watch the meadow to 2100. Says on its face that it is a model, not a forecast.
/pollica/futuresFour frames turning one loop, settling at one, five and ten years. The economics without a spreadsheet.
/pollica/modelEvery candidate program priced and sequenced under a budget cap, so a funding conversation starts from numbers.
/pollica/investOne defect, shown honestly: the old rule deleted disagreement with the 2017 map, the new one draws it.
/before-afterThe whole system with its gaps drawn in. For a technical reader this is the most credible page we have.
/pipelineThe best stand-in we have: speed, sea state, coverage, fuel and hours draining across a working day. It needs the framing that the day is simulated and the depth is not.
/periplusCovered, known, and the difference. Three panels, and they need a survey session pasted in before there is anything to see.
/tesseraA heatwave builds, actions appear by tier, a human accepts or dismisses each one. A strong five minutes, told; a puzzle, opened cold.
/kairosEvery public source for a place, set against the global model: correlation, drift, anomaly. Dense on purpose, and it rewards being read to.
/reckoningThe live heartbeat of every device. It has to be walked, because nothing has reported since 8 July and the page cannot say why on its own.
/tritonPlans a community survey over the real meadow. In no registry, and it overlaps two other planners, so it is shown as a sketch rather than a product.
/pollica/sonarEvery dataset and its provenance, the events log, the project path. Reads as a to-do list to anyone outside the build.
/helmThe open decisions, three at a time, each with its evidence and a recommendation. Internal by construction.
/decisionsDeclared a field-ready health check and currently a print brief with fixed numbers. Held until it reads a real input.
/stewardSeven actors, the tools each touches, and which light up at each stage. A working reference, not a pitch.
/product-mapWhat has been written down, who each piece is for, and what state it is in. A document with no audience named is a draft, whatever its version number says.
The People's Posidonia: the full statement of the project, with the figures and the citations behind them.
/pollica/brief nextA second document of the same name and version sits at /pollica/people. Settle which is canonical.Bottom-up monitoring, argued short. The compressed case, for a reader who will not open eight tabs.
/pollica/pitchWho does what, on what cadence, with what tools. The answer to the first question a large organisation asks.
/pollica/operationsEvery Pollica artifact and every version of it, with the previous states still reachable. The receipt for the versioning rule.
/pollica/versionsThe click-through argument: the problem, the method, the coast, the ask. The front of which this page is the back.
/pollica/partnerA coast that can check its own map, told in the order it is presented. The narrative spine for a live session.
/pollica/run-of-showWho is accountable for what, once the instruments are in the water and we are not standing next to them.
/pollica/operating-modelThe timeline of the teaching week and what each day produced. Note that this and the story page are two separate artifacts.
/pollica/reviewThe pride and action pieces that a town plays round the loop. Community-facing, not technical.
/pollica/toolkitThe one-screen ask aimed at whoever is about to drop an anchor on a meadow. The most public thing we have.
/pollica/anchorThe same toolkit as a map of pieces and how they connect, for planning rather than for reading.
/pollica/mindmapTwo documents currently carry the name pollica-brief-v0_2: one at /pollica/brief and a different one, same title and same version number, at /pollica/people. They differ by about a quarter of their content. Separately, /pollica/review and /pollica/story are two genuinely different documents whose filenames are mirror images of each other, bootcamp-review against review-bootcamp.
Nothing here is broken, and both hazards have the same shape: the filename does not say which document it is. The naming scheme that fixes it, kind plus audience plus version, is drafted and not yet ratified. Until it is, open the link before sending it.
Grouped by where they sit in the data path. The build status is what the code supports, and the next line is the one thing that would move it, not a wish list. The hop-by-hop argument, including what has a synthetic stand-in and what does not, is on the system pipeline.
The sensor fleet view. It works; nothing is reporting into it, and none has since 8 July.
/triton nextA device in the water, then one smoke row against the v1.0.4 contract before the version is promoted.Ingest and fusion, running. Everything it has fused so far was invented upstream.
/reckoning nextNothing, until there is a real row to fuse.Site context intake, reading real sources, feeding the project manifest.
/argus nextPoint it at the next coast, which is the test of whether the intake is portable.Writes the project config every other app reads, and is where the word synthetic enters the system.
/meridian nextNothing pending. It does its job.Runs a survey day and, since v0.8, emits a session file the rest of the chain can read.
/periplus nextImport a plan, so a route drawn in Portolan actually drives the day.Plans a survey and exports a route that nothing currently reads back in.
/portolan nextThe consolidation decision. Until then it plans into a void.Routing. Overlaps Portolan, and both plan over a synthetic distance-to-coast depth.
/pharos nextFold into whichever surface wins, or state why it stays separate.A fourth planner, in no registry, built for a community crew rather than a survey vessel.
/pollica/sonar nextRegister it or retire it. A tool nobody can be told to use is not a tool.The comparison surface. Covered, known and the difference, on one grid, with disagreement drawn rather than deleted.
/tessera nextReal cells. The rule is right; the numbers in it are still invented.The client-facing coast: meadow density, per-zone stress, current conditions, advisories.
/pollica/demo nextConverge its visuals into Tessera rather than maintaining two maps.Risk over inputs that are themselves invented, which makes the number a demonstration of the arithmetic.
/augur nextA no-mask banner, so a surface that cannot see land says so.Explains how a value moves and is scored, with worked examples. Off the delivery path, so being synthetic costs it nothing.
/aqueduct nextNothing. It is doing what it is for.The local twin. A single-box model, not a per-cell simulation, running on synthetic forcing.
/proteus nextTake survey quality as an input, so a better survey visibly narrows the result.Integrates twins that are themselves partial, so it has no fixture of its own to fail against.
/nereus nextWaits on Proteus.Scenarios to 2100 with the economics attached. Prices are sourced; the ecology is the invented half.
/pollica/futures nextFeed it a measured baseline instead of a synthetic one.A finding becomes an action. The object exists; the routing to an owner is thin.
/kairos nextA named owner who can accept, decline or let an action lapse, with the response recorded.Commons and governance scenarios. Nothing here was ever going to be measured; the test is whether the rules are plausible.
/nomos nextTie a scenario to a real decision, which needs a decision object to exist.The open decisions with evidence and a recommendation attached. Choices live in the browser, and the page says so rather than claiming to write a file.
/decisions nextAnswer the three on the shortest clock.Past the act layer the chain stops, and it stops in the places that decide whether any of this was worth doing.
Sprint 010, the survey system: build the picture, then the demo, then the tools underneath it, in that order, so that at close a person who was not in the room can be shown the whole system in one view, watch a simulated survey produce a real artifact, and see that artifact disagree with the 2017 map where it actually disagrees.
The problem set, seven actors, the tools each touches, and which light up per stage. Live at /product-map.
A cell outside the 2017 extent renders as disagreement instead of being discarded. Found en route: the committed landmask was the legacy build and re-deleted the same nearshore cells as land, so it was rebuilt at 60 m.
A session round-trips to disk and back with its provenance intact, and a rebuild is byte-identical.
A simulated day now survives itself: the track, every sounding at the quality it was taken at, the coverage and what the day cost.
What I covered, what was known, and the difference, with an unsurveyed cell visibly distinct from an agreeing one. This is the demo screen the story rests on.
Two grid systems were shipping on one map, hidden only because a layer was off by default. Now one.
A route planned in Portolan drives a Periplus run, and the session points back at the plan it came from. Gated by the consolidation question below.
Brief, demo, review, in three different rooms. First room is the director and a fisherman, because if the run does not look like a real working day the rest is theatre. The objections get written down unedited and become the next brief.
needs a deviceUntil one real reading lands against the current contract, the top of the chain stays untested and two risks have no evidence behind them.
needs a consoleWritten, never applied. It is what would turn a season into a held record, so three later stages wait on it.
needs a decisionFour surfaces plan or run a survey. Which one is the planner gates the plan-to-boat loop.
needs a decisionThe role carries sign-off in the session schema and does not exist in the data model. A name and a permission, or the field is decoration.
The same discipline produced every surface on this page, and it is most of what makes the work checkable by someone who was not there.
A tool gets its slug, role and status in the registry before it gets a file. The unregistered sonar planner above is the exception that proves why: nobody can be told to use it.
Nothing shipped is edited in place. A change copies to the next version and repoints a stable alias, so the previous state stays reachable and any claim about what changed can be checked by opening two tabs.
Local, open, derived, calibrated, synthetic, pending, none. Synthetic is a legal value on purpose, which is what lets a stand-in run in front of a client without pretending.
Verified, partly true, incorrect, or unverifiable, recorded against the source. A claim with no verdict is a draft, not a fact.
A route check confirms every alias resolves to a file that will deploy, and a manifest that proposes a tool for every question fails on purpose, because a system that always has an answer is not answering.
Every figure on every map is synthetic and says so where it is displayed. The protocol is real; the measurement is the next stage, not a claim we are making today.