Forge uses predictable folders for docs, examples, patches, exports, shapes, and repair history.

The exact locations are configurable, but the default structure is intentionally simple.

Simple folder layouts are easier to navigate, troubleshoot, backup, and trust over time.

Especially at 11:43 p.m. when something just renamed 400 notes.

Default Forge Structure

A-I/Forge/Engine/
├── Docs/
├── Examples/
├── Exports/
├── Shapes/
└── Patches/
    ├── vault-patch.md
    ├── Applied/
    ├── Backups/
    └── Reports/

Additional configured paths:

A-I/Forge/Schema/schema.md
A-I/Forge/Exports
A-I/Forge/Inbox
A-I/Forge/Shapes

Folder Meanings

Folder	Purpose
`A-I/Forge/Engine/Docs`	Installed Forge documentation and walkthroughs
`A-I/Forge/Engine/Examples`	Starter schemas, patches, shapes, and reusable workflow examples
`A-I/Forge/Engine/Patches`	Active patch note and patch execution history
`A-I/Forge/Engine/Patches/Applied`	Archived applied patch notes
`A-I/Forge/Engine/Patches/Backups`	File backups created before patch operations
`A-I/Forge/Engine/Patches/Reports`	Patch reports, summaries, and restore manifests
`A-I/Forge/Exports`	Lint reports, exports, relationship indexes, and generated summaries
`A-I/Forge/Shapes`	Shape definition notes and reusable structure templates

Installed Documentation

Forge installs documentation directly into your vault instead of opening external websites or hidden plugin panels.

That means the docs are:

searchable
linkable
editable
syncable
usable offline

The docs behave like normal Obsidian notes.

You can:

bookmark them
annotate them
link to them
customize them
move them
copy sections into your own systems

Examples Are Meant to Be Copied

The Examples folder is intentionally practical.

These are not abstract demos.

They are meant to be:

copied
modified
adapted
reused

Examples include:

starter schemas
patch workflows
repair examples
export workflows
shape systems
maintenance routines

Most users should start by modifying examples instead of building everything from scratch.

Why Forge Keeps Operational Files Visible

Forge stores operational data inside the vault on purpose.

That includes:

reports
exports
backups
repair manifests
patch history
dashboards

This keeps maintenance workflows transparent and reviewable.

Nothing disappears into hidden plugin storage.

You can inspect what Forge generated at any time.

Local Edits Are Respected

Forge does not overwrite installed documentation or examples automatically.

If you customize installed notes, your edits remain intact.

The installer skips files that already exist.

This allows the docs and examples to evolve into part of your own vault workflow over time.