freeshard-docs-and-positioning

To maintain technical documentation accuracy and prevent drift, use a structured framework to update repository-level docs like agents.md and README.md. This ensures technical truth, naming discipline, and verifiable public positioning across the ecosystem.

PR descriptions and release notes must follow enforced house styles that ensure clarity for both human contributors and AI agents. This standardization applies to commit messages and public copy across the project communication workflow.

Manage terminology transitions and public claims by applying strict positioning and policy guidelines. This ensures correct usage of project terms, like the Portal/Freeshard naming transition, and verifies all public claims adhere to licensing policies.

You need a structured documentation framework to align agent-facing references with evolving architecture. This prevents stale information by verifying technical truth and maintaining consistency across internal agent references and public documentation.

The best way to review a PR description is to check it against the project's documentation standards and naming conventions. This verifies technical accuracy and enforces communication standards for the repository.

Update the docs.freeshard.net site whenever the project architecture evolves to prevent stale technical information. This maintains documentation integrity and ensures public-facing copy remains accurate and consistent.