divedog← All selected work

Agent-managed web publishing · fictional demonstration

CLEAN-ROOM RECREATIONSYNTHETIC JOURNEYNO LIVE PUBLISHING

Travel Journal by Conversation

A fictional, reviewable publishing flow that turns a short traveller update into a proposed journal entry—then checks that every connected record agrees before showing a static preview.

Remote usabilityHuman confirmationConsistency guardKnown-good recovery

The problem

When someone is away from a desk, a short update should not require manually reconciling a written entry, an overview record, and a map marker. The hard part is not drafting words; it is keeping connected content clear, deliberate, and recoverable.

Harbour Square

“Arrived after lunch. The market awnings made a good first stop, then I found a quiet bench by the water.”

SYNTHETIC GRAPHIC
AWNING + WATERFRONT

Signal Hill

“Took the slow path to the lookout. Cloud moved across the ridge, so the afternoon note stays brief.”

SYNTHETIC GRAPHIC
RIDGE + CLOUD

Paper Lantern Lane

“A small evening walk, warm lights, and a final meal. Ready to close the three-day journal.”

SYNTHETIC GRAPHIC
THREE LANTERNS

My bounded contribution

I translated a publishing pattern into a deliberately constrained demonstration: structured drafting, explicit confirmation, a one-to-one consistency check, and a clear recovery path. This public page is newly authored and uses no private messages, locations, images, routes, or source code.

ConversationA short fictional update enters a bounded workflow.
Bounded agentOnly proposes structured fields; it does not publish.
Content draftText and optional synthetic image note are staged.
Human confirmationA person approves the proposed entry.
Three updatesArticle, post registry, and map record move together.
Consistency guardCounts and identifiers must agree before preview.
Static previewOnly a validated, local representation is shown.

Architecture in one line: Conversation → bounded agent → content draft → human confirmation → article + registry + map proposed update → consistency guard → static preview.

What this demonstrates

The screen below is a static, deterministic explanation, not a connected journal. It shows how a single fictional update can remain readable while its related records are prepared and checked together.

Known-good proposal

FIELD NOTES JOURNEY · DEMO-030“A small evening walk, warm lights, and a final meal.”

PROPOSED ARTICLE

Paper Lantern Lane · A brief final note from a fictional journey, written from the supplied update and held for confirmation.

Optional image observation: “three warm points of light” — a synthetic description only.

Three records, one check

  • ArticleDEMO-030READY
  • Post registryDEMO-030READY
  • Map registryDEMO-030READY
ARTICLE
1
POST RECORD
1
MAP RECORD
1

Validation and recovery

A known-good path is useful only when the failure path is equally clear. The second panel is an opt-in scenario: it describes a missing record that the guard rejects before any static preview is shown.

Known-good path

After a person confirms the draft, the proposed article, post record, and schematic map point share the same synthetic identifier.

  1. Confirm the staged draft.
  2. Compare one article, one post record, and one map record for DEMO-030.
  3. Allow the static preview only when all three agree.

Opt-in missing-registry scenario

REJECTED BEFORE PREVIEW — imagine the map record for DEMO-030 is absent. The guard stops the proposal rather than presenting a partial journal.

  1. Flag the missing map registry entry.
  2. Keep the last known-good journal state intact.
  3. Offer a restore to the known-good state before a new proposal is reviewed.

Learning, boundaries, and transferable value

The design focuses on the practical disciplines behind a calm interface: small inputs, visible checkpoints, defensive state handling, and a human who remains accountable for what is shown.

Learning

Content workflows benefit from treating connected records as a unit. A concise update can stay lightweight without making the final state ambiguous.

Transferable skills

Requirements translation, structured data design, validation, exception handling, usable feedback, and maintaining a clear operational boundary.

Demonstration limit

This is a static clean-room recreation. It does not send messages, analyse real images, publish content, access a map service, or represent a live backend.

  • Synthetic onlyFictional traveller, generic planar locations, fixed demonstration dates, and freshly authored updates.
  • No live publishingNo live journal, backend, service, account, or external request is used or implied.
  • No private source mirrorNo clean private source mirror was used or available for this reconstruction.
  • Static recovery storyThe acceptance and rejection paths explain intended safeguards; they are not proof of a connected workflow.