# AccuroTech Internal Shape Payload Website Build Prompt

**Version:** 0.1.0  
**Status:** Fresh-session implementation prompt for building the internal editable AccuroTech website.  
**Created:** 2026-06-17  
**Purpose:** Create an internal-facing, clickable, editable company-wide AccuroTech website whose pages render from and save back to Shape Payload `.json` files.  
**Payload safety:** Do not add secrets, credentials, private keys, live tokens, deployment secrets, private customer payloads, concrete private observations, or fabricated production/customer claims.

---

## Role

You are a senior product-minded full-stack implementation agent working in a fresh repository-aware session. Build an internal AccuroTech ecosystem website from the repository's Shape Payload JSON files.

The site is not a public marketing site first. It is an internal identity-building, ecosystem-understanding, editing, and canon-development tool.

Do not use Node or any other server.

These pages should be built as vanilla .php files, which assume that the .json files are loaded on the server in the same file/folder configuration as in the Github repository.

---

## Core Architectural Rule

Everything visible on the website must come from **Shape Payload** `.json` files. Everything editable on the website must save back to Shape Payload `.json` files.

Maintain three separate concepts:

1. **Shape Pattern Template** — reusable structure, stored under `shape_payloads/pattern_templates/`.
2. **Shape Payload** — instantiated data/content payload, stored under `shape_payloads/instances/`.
3. **GitHub Shape Instantiation** — repository-specific binding metadata, stored under `shape_payloads/instances/github_shape_instantiations/`.

A company profile Shape must remain independent from the GitHub repository instantiation of that company profile Shape.

---

## Required Reading

Read, at minimum:

1. `shape_payloads/shape_payload_registry.json`
2. all files under `shape_payloads/pattern_templates/`
3. all files under `shape_payloads/instances/company_profiles/`
4. all files under `shape_payloads/instances/website/`
5. all files under `shape_payloads/instances/github_shape_instantiations/`
6. `docs/company/project_index.md`
7. `docs/company/ecosystem_map.md`
8. `docs/company/values_stub.md`
9. `docs/public/website_content_stub.md`
10. `accurotech_seed_document_v0_0_1.md`
11. `accurotech_portashape_global_shape_catalogue_seed_dayone_base_v0_0_1.json`

If application framework files do not exist, scaffold a simple maintainable application in the repository. Choose a lightweight stack that can read and write local JSON files in development.

---

## Website Requirements

Build pages for:

1. Home / ecosystem overview.
2. Company/project index.
3. One page for each company/profile payload.
4. One section view for each section inside each company/profile payload.
5. Shape Payload registry browser.
6. Shape Pattern Template browser.
7. GitHub instantiation browser.
8. Missing-values / review-needed dashboard.

Each company/profile page must show:

- display name;
- slug;
- entity type;
- aliases;
- related domains;
- source namespaces;
- source Shape IDs;
- canon status;
- review status;
- public-copy approval status;
- all website sections;
- source references for each section;
- relationship references;
- link to the GitHub instantiation payload;
- link to the raw Shape Payload JSON.

---

## Editing Requirements

Make everything practical and editable:

1. Every section body should be clickable to edit.
2. Profile metadata should be editable where allowed by `editable_fields`.
3. Protected fields such as `shape_payload_id` and `conforms_to_shape_pattern_template` should be visible but not casually editable.
4. Save edits back to the source Shape Payload JSON file specified by the page payload `edit_bindings.save_target`.
5. Preserve JSON formatting.
6. Validate required fields before saving.
7. Show source provenance next to edited content.
8. Add a small change/audit record if practical; if not practical, leave a clear TODO in code and documentation.
9. Never write edits into `shape_payloads/pattern_templates/` unless editing templates through a specific template-editing screen.
10. Never confuse the GitHub instantiation payload with the company profile payload.

---

## Navigation Requirements

Everything should be clickable:

- project cards link to project pages;
- Shape IDs link to catalogue/Shape detail views when available;
- source file paths link to raw/source views in the internal app;
- payload IDs link to payload detail views;
- relationship refs link to related company/profile pages;
- edit buttons open inline editors or editing panels;
- breadcrumbs should show where the user is in the ecosystem.

---

## Content Interpretation Requirements

Infer what is important for the internal site by prioritizing:

1. AccuroTech ecosystem identity.
2. The core triad: XtraType meaning, CRE8 authority, PortaShape structure.
3. Project/company role inside the ecosystem.
4. Shape Catalogue alignment.
5. Known fields and unresolved fields.
6. Internal build direction.
7. Review and canon status.
8. Payload safety and source provenance.

The site should help AccuroTech build itself from the inside. Avoid public-marketing gloss unless the repository has public-approved copy.

---

## Implementation Requirements

1. Add application code only after inspecting the repository.
2. Keep the implementation simple and transparent.
3. Prefer local JSON file reads/writes over a database for the first version.
4. Add README or developer notes explaining how to run the site.
5. Add validation utilities for Shape Payload JSON files.
6. Add tests or checks for JSON validity and basic route/data loading.
7. Do not claim deployment readiness unless actually implemented and tested.
8. Take a screenshot if the environment supports running the app and a visible UI is changed.

---

## Expected Final Result

A successful session should produce:

1. A runnable internal website application.
2. Pages for every company/profile payload.
3. Editable sections that save to Shape Payload JSON files.
4. Browsable Shape Payload registry and templates.
5. Clear separation between abstract profile payloads and GitHub repository instantiations.
6. JSON validation checks.
7. Documentation describing how to run and edit the internal site.
8. A final report citing changed files and listing tests/checks run.

End by saying:

> The AccuroTech internal Shape Payload website is ready for review. It renders company identity and ecosystem pages from editable Shape Payload JSON files while keeping abstract Shapes, Shape Payloads, and GitHub repository instantiations separate.