Agency Foundation

> **Document ID:** V01-FND-001  
> **Version:** 1.0.0  
> **Owner:** Executive  
> **Status:** Approved  
> **Last reviewed:** 2026-07-26

# Volume 1 — Agency Foundation

## Purpose

Volume 1 defines the company-wide operating foundation for Steady
Technologies. It turns the architecture in
[Volume 0](../architecture/V00-Master-Architecture.md) into rules employees,
managers, contractors, systems, and governed agents can apply consistently.

## Scope

This volume governs:

- company identity and system philosophy;
- organizational and decision authority;
- communication and documentation;
- quality and knowledge management;
- AI use and human accountability;
- the client lifecycle;
- roles, risk, performance, improvement, and maturity.

Department volumes specialize these rules. They may add stricter controls but
may not silently weaken company-wide policy.

## Audience

- New employees use the volume to understand how Steady operates.
- Managers use it to assign accountability and make controlled decisions.
- Department owners use it when writing SOPs and defining measures.
- Agent and automation builders use it to implement safe operating boundaries.
- Reviewers use it to assess conformance and release readiness.

## Principles

1. Volume 0 governs every interpretation.
2. One document owns each policy subject.
3. Examples clarify policy but never create policy.
4. Human roles remain accountable for consequential decisions.
5. Requirements must be measurable or supported by review evidence.
6. A policy is incomplete without ownership, application, exceptions, and
   escalation.

## Detailed Guidance

### How to read Volume 1

Read [Mission](01-Mission.md) through
[Business System Thinking](05-Business-System-Thinking.md) first. These files
establish why the company exists and how work is framed. Then read the
governance and operating-control documents relevant to your role. Use
[SUMMARY.md](SUMMARY.md) for the complete sequence.

### How to apply a policy

1. Confirm the document status is Approved.
2. Identify whether the policy applies to the work, role, risk, and lifecycle
   stage.
3. Follow the canonical requirement and linked procedure.
4. Record required evidence and approval.
5. Escalate ambiguity or conflict; do not invent an exception.

### Ownership and review

The owner named in each document is accountable for subject accuracy.
Knowledge Management owns structure, links, controlled terminology, and review
tracking. Material changes follow
[Documentation Standards](09-Documentation-Standards.md) and are recorded in
[Revision History](20-Revision-History.md).

## Examples

**Correct application:** A Website team member planning a launch follows the
Website department SOP, then applies the company-wide quality gates in
[Quality Management](10-Quality-Management-System.md). The SOP may require
additional browser testing; it may not remove documented QA.

**Correct conflict handling:** An agent definition appears to permit publishing
an advertisement without approval. The operator stops the release, follows
[AI Governance](12-AI-Governance.md), and corrects the agent definition. The
agent file does not override company policy.

## Best Practices

- Start from the business outcome, not the requested artifact.
- Link to the canonical rule in work records and handoffs.
- Record evidence while work occurs.
- Improve a policy at its source when repeated exceptions reveal a defect.
- Use the glossary when a term has operational consequences.

## Common Mistakes

- Treating a summary, example, prompt, or agent file as governing policy.
- Copying a policy into another document and allowing the copies to diverge.
- Applying a Draft document as if it were approved.
- Skipping an approval because the work was generated automatically.
- Starting a later volume before the active volume passes its release gate.

## Actionable Checklist

- [ ] I have read Volume 0 and the foundation documents relevant to my role.
- [ ] I verified the status and version of the policy I am applying.
- [ ] I used the canonical document rather than a copied excerpt.
- [ ] I identified the accountable owner and required approval.
- [ ] I recorded evidence required by the policy.
- [ ] I escalated any unresolved conflict or exception.

## Related Documents

- [Volume 0 — Master Architecture](../architecture/V00-Master-Architecture.md)
- [Volume 1 summary](SUMMARY.md)
- [Repository roadmap](../../ROADMAP.md)
- [Contribution policy](../../CONTRIBUTING.md)
- [Style guide](../../STYLE_GUIDE.md)