@indigenux/indi-web

Standalone durable website platform generator package for Indi / IFP workspaces.

@indigenux/indi-web is intentionally separated from the Indi reference implementation. The package boundary is:

• indi/ contains the Indi reference implementation and SDK surfaces.
• ifp/ contains protocol specifications, schemas, conformance assets, and release evidence.
• packages/indi-web contains the canonical web generator package.
• generators/indi-web is a compatibility pointer only.

This package contributes the website generator manifest, catalogs, templates, policies, presets, plugin manifests, lifecycle fixtures, and web-platform documentation.

Package identity

| Field | Value | |---|---| | npm package | @indigenux/indi-web | | generator ID | indi-web | | package identity | @indigenux/indi-web | | target kind | website | | canonical path in this repo | packages/indi-web | | legacy in-tree path | generators/indi-web |

Boundary rule for new generators

New generators should follow this package pattern: independent package root, own manifest, own exports, own catalogs, own fixtures, own docs, own package validation. They should not be added as canonical source inside the Indi reference implementation tree.

Validation

npm run catalog:check
npm run boundary:check
indi generator validate . --json
indi generator test . --json
indi generator pack . --dry-run --json

Published contents

The package exports the runtime descriptor, generator manifest, readiness file, catalogs, templates, policies, presets, plugin manifests, fixtures, and docs through package.json exports and files.

indi-web

indi-web is now cataloged as a durable website platform generator. It adopts the full recommendation set: must-have, nice-to-have, and pie-in-the-sky capabilities, policies, operations, extensions, templates, plugins, presets, and fixture evidence, staged according to the practical seven-phase build order.

The adoption is represented in:

• indi.generator.json for generator-level inventory and lifecycle contract.
• catalog/adoption-catalog.json for complete machine-readable coverage.
• catalog/*.json for focused capability, policy, operation, extension, template, plugin, preset, fixture, and build-order inventories.
• docs/*.md for human-readable implementation guidance.
• templates/*.template.md for template placeholders and ownership markers.
• policies/*.policy.json, plugins/*.plugin.json, and presets/*.preset.json for extension-ready package metadata.
• fixtures/* for baseline and expanded evidence scenarios.

Conformance honesty

This package adopts the recommendation inventory and required evidence shape. It does not assert a new runtime conformance certification by itself. IFP-Distributed and IFP-Enterprise surfaces remain preview-labeled until executable suites produce reproducible result hashes.

Practical build order

| Order | Phase | Goal | | --- | --- | --- | | 1 | phase-1-harden-generator-core | Make Plan-first lifecycle, anatomy, ownership, deterministic evidence, and fixture proof the non-negotiable substrate. | | 2 | phase-2-durable-web-platform | Emit architecture, security, accessibility, SEO, performance, testing, CI, docs, and operations baselines. | | 3 | phase-3-policy-packs | Turn web architecture, security, accessibility, SEO, performance, testing, docs, upgrade safety, and extension rules into structured policies. | | 4 | phase-4-extension-surfaces | Expose capabilities, templates, presets, migrations, adapters, hooks, task adapters, and transform profiles through permissioned extension metadata. | | 5 | phase-5-brownfield-adoption | Analyze existing web applications without destructive mutation and classify generated/custom/shared/unknown ownership. | | 6 | phase-6-enterprise-controls | Add trust policy, registry integrity, signing hooks, audit events, SBOM/provenance, CI governance, and organization policy overlays. | | 7 | phase-7-fleet-distributed | Support target-indexed manifests, drift partitions, worker leases, distributed evidence, staged migrations, and fleet governance. |

Catalog counts

| Area | Count | | --- | --- | | capabilities | 26 | | policies | 23 | | operation types | 27 | | commands | 13 | | extension surfaces | 20 | | templates | 34 | | plugins | 25 | | presets | 21 | | expanded fixtures | 16 |

Run npm run catalog:check inside this package to parse the main catalog and generator manifest.