Configuration and Files

Project Configuration

Entry file:

.fe-harness/project.yaml

It declares:

• Harness package and version.
• Project name and product type.
• platform selection.
• stack adapter.
• facts file paths.
• command mappings.
• verify modes.
• Optional sources, ui, api configurations.

Key Facts Files

File	Purpose
AGENTS.md	Project's unique constraint ontology
docs/PROJECT_MAP.md	Module map
docs/CURRENT_STATUS.md	Current status and limitations
docs/PRODUCT.md	Product facts
docs/DESIGN.md	Design facts
docs/DECISIONS.md	Long-term decisions
docs/IMPLEMENTATION_COVERAGE.md	Requirement coverage

Generated Reports

tmp/fe-harness/

This directory is ignored by Git. Reports can serve as local debugging and CI artifacts.

Generated Interface Files

src/types/api.generated.ts
src/services/api.generated.ts
.fe-harness/api/generated.json

These files are protected by managed metadata.

Rules Directory

.fe-harness/rules/

Stores Harness-managed rule files, maintained by optimize --groups rules and validate. Rule files cover engineering standards, verification requirements, module boundaries, and other constraints. Files in this directory are protected by managed metadata; idempotent upgrades only update files with diffs.

Codebase Map Directory

.fe-harness/codebase/

Generated by inspect --map, contains 5 codebase maps:

File	Content
STACK.md	Tech stack and dependencies
STRUCTURE.md	Module and directory structure
CONVENTIONS.md	Code conventions and standards
TESTING.md	Testing strategy and coverage
CONCERNS.md	Concerns and risks

This directory is ignored by Git. Maps can be regenerated and are not protected as managed files.