# Shape Payload Internal Website Architecture

**Status:** Day-Three architecture seed.  
**Created:** 2026-06-17.  
**Purpose:** Redesign the repository approach so internal website content is stored in editable Shape Payload JSON files instead of only Markdown stubs.  
**Payload safety:** This architecture excludes secrets, credentials, private customer payloads, concrete private observations, deployment secrets, and fabricated implementation claims.

## Redesign Summary

The repository now separates three layers that were previously blended together in documentation stubs:

1. **Shape Pattern Templates** define reusable structures.
2. **Shape Payloads** instantiate those templates and hold editable company/profile and website data.
3. **GitHub Shape Instantiations** record how a payload is bound to this repository, source files, extraction rules, and edit policy.

This means the company profile Shape and related Shapes can exist independently from any GitHub repository representation. The GitHub-specific files are only instantiation bindings.

## New File Areas

- `shape_payloads/pattern_templates/` contains reusable Shape Pattern Template JSON files.
- `shape_payloads/instances/company_profiles/` contains one editable company/profile Shape Payload per AccuroTech company, project, ministry, or property.
- `shape_payloads/instances/github_shape_instantiations/` contains repository-specific bindings for those profile payloads.
- `shape_payloads/instances/website/` contains internal website page payloads and the site manifest.
- `shape_payloads/shape_payload_registry.json` lists all current templates and payload files.
- `prompts/website/fill_shape_payload_true_values_prompt.md` directs a fresh LLM session to replace placeholder or weak values with repository-grounded true values.
- `prompts/website/create_internal_shape_payload_website_prompt.md` directs a fresh LLM session to build the editable internal website.

## Internal Website Model

The internal website should render from `shape_payloads/instances/website/internal_site_manifest.json` and the registry. Company pages should use `shape_payloads/instances/website/<slug>.json`, which points back to `shape_payloads/instances/company_profiles/<slug>.json` as the save target.

Every visible company section should be editable and should save back to the relevant Shape Payload JSON field, not to Markdown stubs.

## Review Boundary

The initial Shape Payloads are an architecture seed. Some section bodies intentionally remain extraction instructions or scaffold summaries until `prompts/website/fill_shape_payload_true_values_prompt.md` is run in a fresh repository-aware session.