# Standards

<!--
IndexTitle: Standards Folder
IndexDescription: Reusable rules and conventions agents follow across GetEstablished repositories.
IndexType: README
IndexStatus: Active
LastEdited: 2026-06-08
-->

## Purpose

Standards are reusable rules agents follow across repositories. They define durable conventions for repository structure, naming, documentation, reporting, indexing, and other practices that should stay consistent beyond a single task.

Use this folder for guidance that is stable enough to apply repeatedly and generic enough to be useful across GetEstablished repositories or future project roots.

## What Belongs Here

- Documentation structure standards.
- Naming, indexing, and metadata conventions.
- Repository role and folder boundary rules.
- Short reusable rules that apply across multiple folders or repositories.
- Cross-repository guidance that should not live inside one project plan.

## What Does Not Belong Here

- Project plans, audits, reviews, or backlog notes. Use `Plans`.
- Copy-ready prompts or workflow instructions that are not yet standards. Use `Capabilities`, `Plans`, or future `Skills` depending on role.
- Setup logs or local environment notes. Use `Workspace` or `Plans` until reusable guidance is extracted.
- Website, product, or publishing content. Use `Content`.
- Owner-specific drafts, assets, or scratch notes. Use `Workspace`.

## Important Files

- `RepositoryCoreStandard.md` - repository roles, capability and skill registries, provisioned structure, and indexing profiles.
- `CapabilityProvisionedStructure.md` - setup-owned folders and lazy initialization when paths are missing.
- `RepositoryArchetypeAndCapabilityTiers.md` - universal, archetype, and commissioned capability tiers.
- `FolderReadmeStandard.md` - standard for folder README files and index comments.
- `IndexHealthStandard.md` - domains for index health checks before or during Indexing refresh.
- `MarkdownIndexMetadataStandard.md` - metadata block standard for important Markdown files, capability files, skill files, and future repository indexes.
- `NamingStandard.md` - naming guidance for files, folders, roles, and agent workflow terminology.
- `CapabilityMetadataStandard.md` - Capability module metadata and Harmonization Metadata sections.
- `AgentSituationalAwareness.md` - Cursor vs ChatGPT planning; when cloud review workflows apply.
- `SourceOfTruthAndMirrorStandard.md` - local Git, GitHub, optional cloud review; Git not connected to cloud.
- `CrossPlatformRepositoryPaths.md` - platform-neutral path language; local-primary variants (Draft).
- `NamingStandard.md` §Environment-Adaptive Model - formal terms; deprecated brainstorm aliases.
- `IdeaCaptureTemplate.md` - standard shape for one Idea from chat or notes.
- `PlanTemplate.md` - standard scaffold for new `Plans/` files.
- `PromotionChecklist.md` - Idea → Plan → Capability / Standard promotion stages.
- `ArchiveAndDeprecationRules.md` - supersede, redirect, archive, and delete policy.

## Agent Notes

Add standards only when they help future work stay consistent. Keep them short, reusable, and easy for agents to follow quickly.
