Exports

Exports are Flint's publishing layer. They turn a root note in the Mesh into a built artifact that other people, other Flints, or external systems can consume.

This matters because Flint is not only for private workspace reasoning. It also needs a clean way to publish the outcomes of that reasoning.

How Exports Are Declared

Exports are stored in flint.toml under [exports].required.

[exports]
required = [
  { name = "Guide", file = "Guide.md", mode = "mesh" },
]

Each declaration records:

the public export name
the source root file
the export mode, which is currently mesh
optional depth

The Usual Workflow

Most teams do not write these declarations by hand first. The normal flow is:

tag a Mesh note with #export
run flint export scan
confirm the discovered export declarations
build them with flint export build

You can also add one directly:

flint export add Guide.md Guide

Main Commands

flint export list
flint export scan
flint export add <file> <name>
flint export remove <name>
flint export build
flint export build <name>

What a Build Produces

Built exports are written to:

Exports/(Mesh Export) Name/

That output includes:

exported Mesh/ content
copied Media/ files when needed
_manifest.json

What the Builder Actually Does

The current export builder walks outward from the declared root note and then:

follows the note graph
rewrites wiki links for the built output
expands embeds
copies referenced media
removes stale built export folders before rebuilding

This keeps the built export self-contained enough to be copied, consumed, or sourced by another Flint.

Why Exports Matter to the Wider Flint Model

Exports are one of the bridges between private workspace reasoning and reusable published knowledge.

They are also how one Flint can feed another through source mesh exports. A source Flint builds an export, and another Flint can then pull that built export into Sources/.

Registry Integration

When exports are listed or built, Flint refreshes the workspace's registry entry so other Flints can discover which export names are available locally.