Structure files

---
strictness: moderate
---

# Repository organization

Route reusable agent instructions and supporting resources to agents. Route company-wide knowledge, strategy, and policies to company. Route ongoing responsibilities, processes, and relationships to the team that owns them under teams. Route initiatives with a defined outcome and lifecycle to projects.

Give each entity or topic one primary record. Search for an existing record before creating another. Combine relevant information from several sources into that record and link to detailed evidence instead of copying the same content into several places.

Use lowercase-hyphen names except for required names such as SKILL.md. Create folders only when substantive content needs them; do not create empty folders or placeholder files.

If information could belong in several places, use the most specific existing home. If no destination is clear, report the ambiguity rather than guessing. Surface top-level folder changes, record merges, and deletions for review.

---
strictness: firm
---

# Sales knowledge

Organize account knowledge into one lowercase-hyphen folder per company under customers or pipeline. Use HubSpot to determine the account location, status, and owner. Keep shared sales definitions and processes in rev-ops. Do not infer CRM status from meetings or messages.

Each company folder contains overview.md: a concise synthesis of the relationship, verified contacts, needs, key developments, risks, and next steps from HubSpot and clearly matched Slack conversations. Link material claims to their evidence. Keep detailed records in meetings, support, and contacts subfolders, creating those folders only when substantive content exists.

Keep one dated file per HubSpot meeting note and preserve the complete note word for word, including links. Match the source meeting to its existing file when it changes. Keep one support file per distinct issue and one contact file per person.

Search customers and pipeline before creating a company folder. Avoid duplicates, unsupported facts, empty folders, and updates that only repeat CRM activity counters. Surface company moves, merges, renames, and deletions for review.

---
strictness: strict
---

# Company policies

Maintain one Markdown file per published policy from the Confluence HR Policies space.

Copy each policy word for word. Preserve its headings, lists, tables, visible text, and links. You may convert the formatting to equivalent Markdown, but do not summarize, reinterpret, combine, or omit content. Include the Confluence page link separately so the source remains traceable.

Treat the Confluence page as the stable identity of the policy. When its content or title changes, update the existing file instead of creating another one.

Exclude drafts, comments, meeting notes, and pages outside the HR Policies space. If a source policy disappears, surface it for review instead of deleting the repository copy.

---
strictness: moderate
---

# Projects

Keep one lowercase-hyphen folder per project. Each project has an overview.md that concisely combines verified information from its project documents and clearly matched team discussions.

Organize the overview into Goal, Owner, Status, Scope, Milestones, Risks, and Next steps. Update it when a source changes a material fact. Do not infer an owner, commitment, date, or completion status that no source confirms.

Keep one dated file per meeting in meetings and one dated file per decision in decisions. Link those records from the overview where they support a claim. Preserve earlier decisions when a newer decision supersedes them so the history remains understandable.

Search for the project before creating a new folder. Do not create empty folders, placeholder sections, or a second project record for a new name or source. Surface merges and deletions for review.