Programs, tutorials, HTML demos, and exemplary files

Tutorial Use

Use as the central prompt and media-production surface for future content, library entries, render briefs, storyboards, sound cues, and AI-model handoffs.

Solution Fit

Creates a safe bridge between protected experimental HTML workbenches and public-facing Artemis content development.

Boundary

Do not publish source HTML, embedded assets, exact Desktop paths, unverified fabrication values, private coordinates, or raw generated code from old prototypes.

Tutorial Use

Use as a finance-education and executive-literacy route for explaining how source income, deductions, taxable income, credits, payments, and scenario choices change the final review picture.

Solution Fit

Broadens Artemis beyond construction controls into financial architecture storytelling, advisory intake, educational products, and premium scenario workshops.

Boundary

Educational prototype only. It is not tax, legal, accounting, filing, or investment advice and should not be presented as production tax software.

Tutorial Use

Use as the foundation for destination storytelling, bilingual cultural-route education, tourism campaign planning, and map-engine reliability notes.

Solution Fit

Creates a revenue path for destination pilots, local partner discovery, itinerary products, sponsorship packages, and public-sector cultural/economic development proposals.

Boundary

Contains a public browser Mapbox pk token. Public pk tokens are not secrets, but they must be URL-restricted to approved domains and never replaced with an sk secret token.

Tutorial Use

Use as the repeatable Time Atlas pattern for KML-authored historical sites, evidence cards, story clips, classroom embeds, and future multi-era cultural geography modules.

Solution Fit

Creates a content and revenue path for archaeology-tech education, museum/tour-guide storytelling, SEO pages, social clip series, and paid site/era packs.

Boundary

Evidence-graded prototype only. The map is a compressed interpretive diorama using KML anchors, not a survey-grade GIS model, official archaeology publication, or navigation product.

Tutorial Use

Use as the first character-led mobile Atlas pattern for simplified itinerary progression, destination world storytelling, reorderable trip planning, KML anchor interpretation, and iPhone game pacing.

Solution Fit

Creates a route for sponsored destination quests, premium character guides, cultural itinerary products, mobile funnel testing, and future booking handoff flows.

Boundary

Approximate route prototype only. It does not use Mapbox, does not expose a map token, and should not be treated as a complete GIS, navigation, or booking product. KML points and destinations are projected onto a designed game board.

Tutorial Use

Best used as an Academy/tutorial extraction source for formulas, input explanations, and estimator education.

Solution Fit

Supports the utility bridge by explaining why quantities, field conditions, crew assumptions, and construction standards change cost and schedule exposure.

Boundary

Do not publish the raw HTML. Public tutorial examples should use synthetic inputs and generic work-package naming.

Tutorial Use

Useful as the blueprint for a future interactive training tool once it is rebuilt with synthetic geometry and browser-safe code.

Solution Fit

Extends the bridge from static executive narrative into time-aware production planning and constructability review.

Boundary

Do not iframe or embed the raw simulator. Any public 3D/time tool must be rebuilt with generic data and reviewed controls.

Tutorial Use

Use as visual-system inspiration for brand narration, not as a tutorial for product capability.

Solution Fit

Supports executive experience design, logo library presentation, and the public brand narrative around implementation confidence.

Boundary

This is a brand-experience reference, not a current product-capability claim.

Tutorial Use

Useful as a private reference for future brand-experience build notes, camera choreography, and optimized 3D presentation guidance.

Solution Fit

Supports the Diana Moonshot showcase as the visual source direction for a future rebuilt public viewer or rendered asset sequence.

Boundary

Do not publish the standalone viewer, embedded model payload, or source code until the viewer is rebuilt and reviewed for licensing, performance, and public messaging.

Tutorial Use

Useful for explaining the implementation method: inputs, disciplines, estimate engine, expert review, and verification gate.

Solution Fit

Primary source direction for the Utility Intelligence Bridge public narrative and future pilot cockpit.

Boundary

Public pages should describe the system pattern without agency names, project identifiers, source HTML, or private formulas.

Tutorial Use

Use as the executive demo path when the room needs both the field-to-cash proof and the polished Cockpit Classic story before discussing a private pilot.

Solution Fit

Strengthens the Utility Intelligence Bridge package by making the RC8.3 to RC8.4 progression visible and comparable on the public website.

Boundary

Do not publish raw HTML, exact GIS context, coordinates, agency/project names, protected formulas, source records, or payment/certification logic.

Tutorial Use

Use as the public contractor-pursuit training path for explaining how award/status data must be joined with due dates, addenda, plan/spec files, requirements, and human review before it becomes bid action.

Solution Fit

Extends Artemis earlier in the contractor lifecycle: opportunity radar and pursuit controls before Utility Bridge handles field-to-cash execution after award.

Boundary

Do not publish raw HTML, embedded record tables, vendor names, contract IDs, EPINs, exact monetary ledger values, source paths, or live procurement decisions.

Tutorial Use

Useful as the primary contractor training path around claims, actuals, field evidence, payment lag, source custody, and review discipline.

Solution Fit

Defines the deeper private pilot direction after the public Utility Intelligence Bridge narrative is accepted, while giving the public site a synthetic live proof.

Boundary

Do not publish raw GIS, actuals, claims logic, project naming, or source HTML. Use only public-safe narrative and synthetic examples.

Tutorial Use

Useful as a private implementation checklist for how public demo files, map treatment, and test evidence should be packaged together.

Solution Fit

Strengthens the Utility Intelligence Bridge proof story by showing the future private-pilot handoff pattern: demo, spatial reference, and validation report.

Boundary

Do not publish the raw package, source HTML, corridor data, actuals, claims logic, agency identifiers, or test-report internals.

Tutorial Use

Use as a demonstration storyline for deductive contract review, inductive pattern detection, abductive issue framing, and multi-model AI check-and-balance review.

Solution Fit

Supports the Artemis claim and contract reasoning narrative: identify requirements, exercise responsibilities, initiate rights timely, and keep evidence gates visible.

Boundary

Do not publish source HTML, delay records, claim names, project identifiers, dates, dollar values, document paths, correspondence, dispute narratives, or legal advice.

Tutorial Use

Use as a demonstration path for model-to-schedule-to-cost reasoning with generic utility construction examples.

Solution Fit

Supports the Utility Intelligence Bridge by showing how standards, geometry, schedule, quantities, and cost coding can become one controlled workbench.

Boundary

Do not publish source HTML, agency labels, utility standards, private model logic, cost-code mappings, project parameters, or raw 3D assets.

Tutorial Use

Use as a public-safe storyline for explaining budget traceability, source-of-truth controls, and executive audit readiness.

Solution Fit

Supports model-to-money and executive finance narratives without exposing raw budget records.

Boundary

Do not publish source HTML, raw budget data, person names, project identifiers, bid items, audit records, or dollar values.

Tutorial Use

Use as a format model for cinematic field education and public knowledge articles.

Solution Fit

Supports the Artemis public storytelling layer by turning technical field context into a narrated, role-aware experience.

Boundary

Do not publish source HTML, project names, organization names, site history, visit details, embedded private narrative content, or raw media.

Tutorial Use

Use as a source pattern for articles and visuals about forecast ranges, cash timing, assumptions, and escalation thresholds.

Solution Fit

Supports the Forecast Exposure Control Center narrative and future public-safe finance/control tutorials.

Boundary

Do not publish source HTML, raw forecast data, project identifiers, budget labels, exposure values, or source formulas.

Tutorial Use

Use as an advanced article format for explaining who owns risk, which category moved, and what executive decision is required.

Solution Fit

Extends forecast exposure storytelling into ownership, accountability, and decision routing.

Boundary

Do not publish source HTML, raw category data, real-party ownership labels, project identifiers, exposure values, or source formulas.

Tutorial Use

Use as the format model for future Artemis education: module promise, build steps, prompt roles, QA checklist, visual idea, and public caveat.

Solution Fit

Supports an AI-assisted publication system where field knowledge becomes reviewed articles, graphics, and implementation playbooks.

Boundary

Do not publish source HTML, private case-study labels, embedded project specifics, or unreviewed AI prompts.

Tutorial Use

Useful for future EN/TR article and lesson formats that teach AI-assisted implementation without exposing private examples.

Solution Fit

Shows how Artemis can teach CEOs, CFOs, project teams, engineers, builders, and operators through role-aware content.

Boundary

Do not publish raw tutorial HTML, private case-study context, project names, coordinates, or unreviewed bilingual translations.

Tutorial Use

Useful as a model for explaining how Artemis articles, tutorials, and visual systems improve over time.

Solution Fit

Supports disciplined publication operations: every release should have version notes, caveats, test evidence, and public boundary language.

Boundary

Do not publish internal source filenames, raw changelog notes, or implementation details that reveal private source material.