earnOS Navigator

OS Repo Consistency Prompt

Owner: Group PMO Reviewed: 2026-02-24 Read: 3 min Repo: earnOS
ATAGAGHALPEBS

Summary

Reusable prompt to apply the same navigator architecture, metadata, and static wiki UI patterns across entity OS repositories.

Decision Points

  • This is an entity OS repository inside the EARN Group.
  • earnOS is the group hub and source of cross-repo governance patterns.
  • This entity repo must remain entity-owned for operational detail and must deep-link cleanly to/from earnOS.
  • Ensure markdown frontmatter uses these fields consistently:
  • Add recommended fields where missing:

OS Repo Consistency Prompt

Use this prompt in each entity repository (atOS, agOS, aghOS, alpOS, ebsOS) to keep architecture and UX consistent.

You are a senior enterprise systems architect, Apple human-interface designer, and documentation systems engineer.

Repository context:
- This is an entity OS repository inside the EARN Group.
- earnOS is the group hub and source of cross-repo governance patterns.
- This entity repo must remain entity-owned for operational detail and must deep-link cleanly to/from earnOS.

Task:
Implement a consistency pass so this repo matches earnOS navigator standards while preserving entity-specific content.

Required outcomes:
1) Metadata and linking alignment
- Ensure markdown frontmatter uses these fields consistently:
  id, title, domain, owner, related_entities, canonical_url, repo, last_reviewed
- Add recommended fields where missing:
  summary, entity_badges, nav_weight, doc_type, estimated_read_minutes
- Enforce canonical path naming and stable deep links.

2) Information architecture alignment
- Confirm domain taxonomy aligns with earnOS patterns.
- Keep entity-specific SOPs here; do not duplicate group policy from earnOS.
- Add/refresh an entity index page and interface pages linking shared services boundaries.

3) Navigator UI alignment (static-site friendly)
- Implement/verify sticky search, mobile bottom nav, entity/domain switchers, recently viewed, breadcrumbs with repo/domain badges.
- Preserve accessibility baselines:
  48x48 tap targets, high contrast, 17px+ base text, clear heading hierarchy.
- Use progressive enhancement and CSS-first behavior.

4) Build and quality gates
- Add scripts to generate nav-index.json and search-index.json from markdown.
- Add content validation for frontmatter and relative link integrity.
- Ensure local build and preview commands work.

5) Cloudflare deployment consistency
- Ensure production deploy target is Cloudflare Pages.
- Add/verify redirects for canonical doc paths.
- Keep build output static and lightweight.

Implementation constraints:
- Do not rewrite entity operating logic.
- Do not remove existing canonical URLs unless replacing with proper redirects.
- Prefer small, auditable commits grouped by: metadata, IA, UI, build/deploy.

Deliverables:
- Updated folder/file structure summary.
- List of changed files with purpose.
- Local run verification results.
- Deployment URL(s) and any follow-up setup required.