Conformance Checklist

This checklist consolidates the requirements for validating project conformance:

• The project root contains FISS/INDEX.md and FISS/BOOTSTRAP.md.
• The root index links to FISS/BOOTSTRAP.md with a read condition requiring it before work begins on the project.
• Every used area is reachable via navigation from the root index; composite areas contain an INDEX.md linking to their contents.
• Every index navigation link includes a read condition and resolves to an existing target.
• If overrides are used, the root index links to FISS/overrides/INDEX.md with the read condition "Read before using any skill"; agents check applicable documents before running skills.
• If skills share operational artifacts, default filenames and path override rules are coordinated between skills and project documentation.
• Single-file areas may use project-defined filenames; containers without an index are reachable through navigation of their enclosing area.
• Indexes focus on navigation, while FISS/BOOTSTRAP.md provides concise baseline context.
• For information with multiple sources, an authoritative source or priority rule is defined; unresolved conflicts require explicit decisions.
• If a root agent instruction file (AGENTS.md) is present, it directs agents to FISS/INDEX.md without duplicating space content.
• If a task workflow is documented, applicable rules for handling operational artifacts are specified.

Other areas and mechanisms are introduced as needed.

Structural checks can be automated. A linting tool (e.g., fiss-lint) can verify required files, link integrity, read condition presence, and naming conventions. The standard does not mandate a specific tool or literal Read when marker.

Mechanical validation does not assess accuracy, relevance, or completeness of knowledge. Those responsibilities remain with the project team.