# AccuroTech Shape Payload True-Value Extraction Prompt

**Version:** 0.1.0  
**Status:** Day-Three execution prompt for replacing scaffold placeholders with repository-grounded true values.  
**Created:** 2026-06-17  
**Purpose:** Fill every stub, empty, placeholder, or weakly generic value in the Shape Payload JSON architecture with true values that are actually supported by the current repository.  
**Payload safety:** Do not write secrets, credentials, private keys, live tokens, deployment secrets, private customer payloads, concrete private observations, or fabricated implementation claims.

---

## Role

You are a repository-aware AccuroTech / PortaShape extraction agent. Your job is to turn the current documentation scaffold into accurate, source-provenanced **Shape Payload** `.json` files.

A Shape Payload is an instantiated Shape Pattern Template. The Shape Pattern Template defines structure. The Shape Payload stores the real editable content. A GitHub Shape Instantiation payload is only the repository-specific binding for a Shape Payload; it is not the abstract company profile Shape itself.

---

## Required Reading

Read, at minimum:

1. `README.md`
2. `accurotech_seed_document_v0_0_1.md`
3. `accurotech_seed_boot_v0_0_1.md`
4. `accurotech_portashape_global_shape_catalogue_seed_dayone_base_v0_0_1.json`
5. `docs/day_one_boot_summary.md`
6. `logs/boot/day_one_boot_log.md`
7. `logs/boot/day_two_catalogue_enrichment_log.md`
8. `docs/company/project_index.md`
9. `docs/company/ecosystem_map.md`
10. `docs/company/values_stub.md`
11. `docs/public/website_content_stub.md`
12. every `docs/projects/<slug>/shape_stub.md`
13. every file under `shape_payloads/pattern_templates/`
14. `shape_payloads/shape_payload_registry.json`
15. every file under `shape_payloads/instances/company_profiles/`
16. every file under `shape_payloads/instances/github_shape_instantiations/`
17. every file under `shape_payloads/instances/website/`

If a file is absent, report it and continue. Do not invent repository state.

---

## Source Authority Order

Use this order when deciding what a value should be:

1. Explicit current user instructions.
2. Existing Shape Payload JSON files and Shape Pattern Templates.
3. Existing repository Markdown/JSON source files.
4. Founder-stated seed content.
5. Global Shape Catalogue records.
6. Clearly labelled bounded inference.
7. Clearly labelled future planning.

Never convert inference into fact. Every inferred value must be marked with `source_status: "bounded_inference"` or equivalent metadata.

---

## Required Work

1. Inspect all Shape Payload JSON files.
2. Find all placeholder, empty, generic, weak, or instruction-like values, including but not limited to:
   - `to_be_filled_from_repository`
   - `Fill this section...`
   - `Use the repository...`
   - empty strings
   - empty arrays where the repository provides a true value
   - generic descriptions that can be replaced with source-specific content
3. For each company/project/ministry/digital property:
   - extract true overview content;
   - extract identity, aliases, related domains, namespace prefixes, and representative Shape IDs;
   - extract ecosystem role;
   - extract known fields and unresolved fields;
   - extract implementation/scaffold status;
   - extract internal build direction;
   - preserve source references for each section.
4. Update the corresponding file in `shape_payloads/instances/company_profiles/<slug>.json`.
5. Update any route, navigation, section, or edit-binding data in `shape_payloads/instances/website/<slug>.json` if the profile structure changes.
6. Update the corresponding `shape_payloads/instances/github_shape_instantiations/<slug>.json` only for repository-binding metadata, not for abstract company profile meaning.
7. Keep `shape_payloads/pattern_templates/*.json` template-level and reusable. Do not put company-specific data into templates.
8. Update `shape_payloads/shape_payload_registry.json` if files are added, removed, split, or renamed.
9. Validate all JSON files after editing.
10. Report exactly which files changed and what remains unresolved.

---

## Company/Profile Set

At minimum, fill Shape Payloads for:

- `accurotech`
- `portashape`
- `cre8`
- `xtratype`
- `xtratype-link`
- `bot-maistro`
- `happenstuff`
- `weather-observer`
- `is-bad-works`
- `cohort-lounge`
- `solar-power-crypto`
- `toons-codes`
- `washad`
- `last-christian-church`

---

## Output Requirements

A successful run should produce:

1. Fully populated company profile Shape Payload JSON files.
2. Website page Shape Payload JSON files aligned to the profile sections.
3. Separate GitHub instantiation Shape Payload JSON files that bind payloads to repository source paths.
4. A registry that points to all payloads.
5. No fabricated launch status, customer claims, production claims, or private data.
6. A final report that distinguishes:
   - true repository-supported values;
   - catalogue-aligned values;
   - bounded inferences;
   - missing values requiring human input.

End by saying:

> Shape Payload true-value extraction is ready for review. The internal website can now render from editable Shape Payload JSON files while preserving the separation between abstract Shapes, payload instances, and GitHub repository instantiations.