Fortemi Core Prebuilt Indices

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

AIWG release packages emit a prebuilt Fortemi Core v2 index for the `framework` graph:

prebuilt/fortemi-core/framework/aiwg-fortemi-index-v2.json
prebuilt/fortemi-core/framework/manifest.json

The manifest records the graph, schema, generated timestamp, item count, privacy classification, and SHA-256 checksum.

This prebuilt export is the compact metadata/capability projection used so framework discovery can work from the npm distribution without shipping the full framework source body corpus. General source frontmatter is removed during compaction, except for the allowlisted `search.frontmatter.aiwg_script` field. That normalized declaration is runtime-critical: it preserves the entrypoint, runtime, working-directory policy, and argument hint needed by the agent-owned run operation when discovery is using only the packaged index.

the agent-owned index operation first uses a valid local cache under `.aiwg/.index/fortemi-core/`. If no compatible local framework cache exists, it falls back to the packaged prebuilt framework index.

The experimental web-backed `discover` flow downloads the signed release `prebuilt/fortemi-core/framework/manifest.json` and `prebuilt/fortemi-core/framework/aiwg-fortemi-index-v2.json` artifacts, verifies signatures, and caches the result using the manifest digest key used by that web slice.

The older `fortemi` storage backend in `.aiwg/storage.config` remains an alpha MCP persistence adapter and is deprecated for discovery/search routing.

Regenerate the release artifact before packing:

npm run release:fortemi-index

`npm pack` runs this automatically through `prepack`. Local rebuilds are still required when querying project/codebase graphs, when source-body/fulltext fidelity matters, or when the operator needs a private framework cache with locally modified corpus content:

Use AIWG to complete this documented outcome: npm pack runs this automatically through prepack. Local rebuilds are still required when querying project/codebase graphs, when source-body/fulltext fidelity matters, or when the operator needs a private framework cache with locally modifie
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Release-gate discovery expectations live in `test/fixtures/artifacts/release-discovery-matrix.json`. When adding or renaming capabilities, add a matrix case with the user-facing query phrase, expected artifact path/type, and an acceptable rank window.

CI runs the same release gate through:

npm run ci:fortemi-index

That command validates the query matrix against local and Fortemi Core backends, runs `npm pack` through `prepack`, verifies the prebuilt export and manifest are included in the npm tarball, checks manifest checksum/schema and size ceiling, and confirms Fortemi-backed discovery can answer from the packaged fallback with an empty local cache. It also compares source script declarations with packaged records and executes representative script-bearing skills by both canonical name and stable artifact ID from a production-only tarball install.

The npm tarball allowlist includes the top-level `prebuilt/` directory, and the publish workflows run the Fortemi package verification before publishing. That keeps the generated index, manifest checksum, and fallback query behavior part of the release package gate instead of a local-only smoke test.

The general install-size budget includes this intentional distro payload because operators previously paid the same cost by building the framework index locally. The Fortemi package gate still enforces a separate prebuilt export size ceiling so unrelated corpus growth does not silently bloat releases.

Discovery tie-breaks are deterministic. Equal-score default framework results prefer canonical `frameworks/`, `addons/`, and `extensions/` source paths over `plugins/` mirror copies, then sort by artifact type, name/title, and path.