Create a local personal journey with your own AI

Ask your agent: “Please go to map.viguie.info and follow the instructions there to create a map journey about [your subject].” The agent chooses the chapter organisation for your subject.

The homepage and complete authoring kit each contain all instructions, the v3 JSON Schema and an example. Separate instructions, schema and example files are redundant access routes, not additional prerequisites. Once the agent has all three sections, it should continue even if another address is inaccessible; it need not fetch duplicates or ask you to paste them. Historical research and package validation are still required. The result is a ZIP containing journey.json and optional media/, audio/ and geometry/ folders, or those files supplied separately.

Open the local journey importer Download the complete instructions for your AI (.md)

What stays local

The browser reads only files you select. It does not upload, store, research, verify, or publish the journey or its assets. For unresolved v3 place names it sends only the name and supplied geographic hints to HistoriEarth's same-origin API; choices and provenance remain in this import session. HistoriEarth checks its local dataset first. After a definitive local no-match, or a lone unqualified match to a very small populated place, its server automatically sends the place name to Wikidata, filters candidates with applicable alias, place-type and country hints, and identifies any returned candidate and provenance. A weak local homonym is never accepted without the reader's choice. Busy, timed-out or unavailable local lookup never triggers that fallback. Direct image hosts receive their own disclosure. A local journey is visibly marked unverified.

What an agent must supply

Choose 2–18 chronological chapters from the subject’s distinct historical structure. There is no preferred count or threshold at six or seven: do not compress the history to stay below one, and do not pad it to reach one. Several chapters may start in the same year and retain their narrative order.
A declared central subject, claim-to-source bindings, and one source-backed map focus per chapter, plus optional source-backed markers.
Place names and useful country, region, type, historical-name or authority hints; coordinates are optional. The reader chooses or skips ambiguous matches.
Plan the sourced map change chapter by chapter. For travel, investigate primary movement records and route datasets or reconstruction maps before deciding that arrows are impossible; report inspected path evidence or two distinct bounded searches and the gap for a static outcome. Only a sourced corridor can show progressive route arrows, and it must disclose waypoint derivation and defensible spatial precision in the reader's map-provenance panel. Named stops alone support a static schematic connector, never a claimed path. Route vertices need not exactly match the gazetteer's representative points: named straits and islands may be crossed along a route, while city/port landfalls are checked at its ends. Unsupported cape, bay or anchorage stops need source-bound coordinates. Polygon/MultiPolygon areas, dates and deterministic narration actions are supported where pertinent; referenced GeoJSON belongs beneath geometry/. Advanced animation remains deferred.
Aim for three or more strong, distinct images per chapter, up to six. Below three, try at least two materially different follow-up searches when tools and plausible avenues permit, then report the stopping reason or access blocker; one image does not complete research and filler never counts. HistoriEarth resizes and converts supplied images to WebP (up to 2 MiB and 2560 pixels per side). Record complete creator, date, source, licence, attribution, rights, relevance, and distinct-contribution metadata. A browser-only agent may instead provide a declared direct HTTPS image URL; HistoriEarth downloads and checks it on opening. MIME type, byte length and dimensions may be omitted: the importer measures the source and retains only its WebP display copy. Unsupported browsers receive a compatibility warning. Images that cannot be checked receive individual notices.
Optional chapter MP3s in audio/. Without them, the play control requests a browser voice in the package's declared language when available.
Research suitable images during the initial authoring task where tools permit. Each chapter should report mediaResearch.status (completed, blocked or not-started) and a short note, with one delivery-table row per chapter. These are the author's declarations, not verified research. Existing packages may omit the field; a chapter without images or a declaration shows “Media research not reported.”

Use the same deterministic quality floor as private OpenEye authoring while keeping this route fully local. Harm-sensitive chapters require structured declarations, but those checks do not prove historical adequacy or tone. Personally acquired restricted media may be marked personal-private-use only; it stays local and must not be published or redistributed. Never invent historical claims, locations, image rights, or borders.

Download the valid minimal v3 example to test the importer first. It needs no asset folder.

Follow the package self-check. Select the ZIP directly, or the JSON and, if it names local assets, their common containing folder. Resolve any import errors before opening the journey. Portable v3 supports source-resolved points, bounded geometry and deterministic synchronized playback; advanced animations remain deferred.