## Context

ClawFort currently has a single-page news experience and no dedicated policy/disclaimer documents accessible from primary navigation. This creates ambiguity around authorship, verification, and acceptable use expectations.

This change introduces lightweight policy pages and footer navigation updates without changing core data flows or APIs.

## Goals / Non-Goals

**Goals:**
- Add visible footer links for Terms of Use and Attribution.
- Add dedicated pages with explicit non-ownership and AI-generation disclosures.
- Add clear risk language that content is unverified and users act at their own risk.

**Non-Goals:**
- Implementing full legal-policy versioning workflows.
- User-specific policy acceptance tracking.
- Backend auth/session changes.

## Decisions

### Decision: Serve policy pages as static frontend documents
**Decision:** Implement `terms.html` and `attribution.html` as static pages in the frontend directory.

**Rationale:**
- Lowest complexity for current architecture.
- Policy content is mostly static and does not require dynamic API data.

**Alternatives considered:**
- Backend-rendered templates: rejected due to unnecessary server complexity.

### Decision: Add persistent footer links on main page and policy pages
**Decision:** Footer includes links on landing page and reciprocal navigation from policy pages back to home.

**Rationale:**
- Improves discoverability and prevents navigation dead ends.

**Alternatives considered:**
- Header-only links: rejected due to crowded header and lower policy discoverability.

### Decision: Keep disclaimer wording explicit and prominent
**Decision:** Use direct language in page body and heading hierarchy emphasizing AI generation, non-ownership, and use-at-own-risk boundaries.

**Rationale:**
- Meets intent of legal disclosure and user expectation setting.

**Alternatives considered:**
- Compact single-line disclaimers: rejected as insufficiently clear.

## Risks / Trade-offs

- **[Risk] Disclaimer copy may still be interpreted differently by jurisdictions** -> Mitigation: keep language clear and easily editable in static pages.
- **[Trade-off] Static pages require redeploy for copy updates** -> Mitigation: isolate content in dedicated files for quick revision.

## Migration Plan

1. Add static policy pages under frontend.
2. Add footer links in the main page and cross-links in policy pages.
3. Validate page serving and navigation in local runtime.

Rollback:
- Remove policy pages and footer links; no data migration required.

## Open Questions

- Should policy pages include effective-date/version metadata in this phase?
