Skip to main content
Current amendment — 2026-07-10: hello-lucia/lucia-library is the canonical documentation source, published through Mintlify at helloluciallc.com. The library now has three products: Lucia, Lucia Fieldwork, and Eval Labs. The former Obsidian Publish domains remain live legacy, non-canonical surfaces and do not currently redirect here.

​
Status

​
Context

At the time of the original decision, Lucia Canon (docs.hellolucia.ai) and Eval Labs Canon (docs.evaluationlabs.ai) were two separate Obsidian Publish sites with independent navigation, search, and publish.css design systems. The goal was a single unified “library” that grouped the content more clearly and presented the company’s documentation as one coherent home. Mintlify’s Products feature provided a product switcher over distinct documentation trees in one project on one custom domain. The initial migration covered Lucia and Eval Labs; Lucia Fieldwork was subsequently added as a third, separately navigable product. The historical vaults may still be consulted as read-only conversion inputs, but the migration established git/MDX in this repository—not Obsidian or an old Publish site—as the canonical documentation source.

​
Decision

  • Publish a unified Mintlify library with a product switcher and a custom branded landing page.
  • Treat hello-lucia/lucia-library as the canonical source for published documentation.
  • Present three products: Lucia, Lucia Fieldwork, and Eval Labs.
  • Use helloluciallc.com as the canonical documentation domain.
  • Treat docs.hellolucia.ai and docs.evaluationlabs.ai as legacy and non-canonical until separate infrastructure work implements and verifies redirects or retirement. Their continued availability does not give them source-truth status.
  • Keep historical Obsidian vaults read-only and use them only for explicitly approved historical imports.
  • Quarantine scripts/convert.mjs by default so routine documentation work cannot overwrite canonical MDX. Any historical import requires an explicit, reviewed override and a complete candidate-diff review.
  • Do not publish private operational material or rely on hidden/unlisted navigation as access control. Safe historical content must be clearly labeled and kept outside public route reach when it should not be published.

​
Consequences

Easier / better
  • One library, unified navigation, search, and design across all three product documentation homes.
  • Deploys from canonical git content rather than a manual Obsidian Publish step.
  • A neutral parent domain (the LLC) hosts the full product family without making a legacy domain authoritative.
Harder / changed
  • Canonical editing is git/MDX in this repository. Vault conveniences such as wikilinks, graph views, and publish.css are historical conversion concerns, not a second authoring authority.
  • The former publish.css systems are represented through Mintlify theming and MDX components.
  • Historical material needs explicit date/status context so migration records are not mistaken for current system truth.
  • Every file under a Mintlify-served tree must be treated as potentially public; removing a page from navigation is not a privacy boundary.
Truth-state note: This decision governs documentation ownership and publication only. It does not change or prove any product/runtime status. The live library and its source repository must not be used as evidence for application behavior.

​
Historical migration validation

The figures below are preserved as the acceptance snapshot from 2026-06-23. They document the migration event, not the current page count or current publication boundary.
  • Phase 1 conversion complete and pushed to hello-lucia/lucia-library:
    • 782 wikilinks resolved, 0 unresolved; 34 image embeds migrated.
    • 159 pages wired into docs.json (Lucia 93 / Eval Labs 66); 16 legacy pages were unlisted at that time; 12 raw-HTML pages held back for component work.
    • MDX pre-flight clean (no bare <, braces, or autolinks in included pages).
  • Mintlify cloud build, navigation, domain, and publication status subsequently changed; current repository configuration and deployment evidence supersede this snapshot.