# AccuroTech Day Two Catalogue Enrichment Boot Prompt

**Version:** 0.0.1  
**Status:** Day-Two boot-ready scaffold expansion prompt  
**Created:** 2026-06-17  
**Document role:** Follow-on executable boot prompt for moving the Day-One scaffold forward by filling conservative, informative company/project documents from the Shape Catalogue and seed documents.  
**Primary prior Shape:** `PS-BOOT-001 — Day Zero to Day One Bootstrapping Shape`  
**Prior instance:** `AT-PS-BOOT-INSTANCE-001 — AccuroTech Day Zero to Day One Boot Instance`  
**Payload policy:** This prompt may direct documentation, Shape, scaffold, schema, and planning work, but it must not cause private keys, live credentials, access tokens, deployment secrets, concrete private customer payloads, concrete private observations, or other secret operational data to be written into the repository.

---

## 1. Purpose

You are booting into the AccuroTech / PortaShape repository after the initial Day-One scaffold has been created. Your task is to move the scaffold forward into **informative but still conservative documents** for each company, project, ministry, and digital property named in the seed package.

The previous boot prompt instantiated the repository as working memory. This prompt should now use that memory and the global Shape Catalogue to enrich the scaffold without pretending that planned systems are already mature implementations.

The goal is:

1. read the existing seed documents, Shape Catalogue, Day-One summary, logs, instance record, and stubs;
2. extract relevant catalogue and seed information for each company/project;
3. turn shallow `shape_stub.md` files into useful Day-Two documentation pages;
4. create or update index documents that explain how each project relates to AccuroTech, PortaShape, CRE8, XtraType, Bot Maistro, WASHAD, Last Christian Church, and the rest of the ecosystem;
5. preserve a clear distinction between **seed canon**, **catalogue records**, **bounded inference**, **planned work**, **scaffolded work**, and **implemented work**.

---

## 2. Required Initial Reading

Before writing or modifying files, locate and 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. `catalogue/change_records/day_one_boot_shape_registration.md`
8. `instances/AT-PS-BOOT-INSTANCE-001.json`
9. `roadmap/day_two_plan.md`
10. every existing `docs/projects/<project-slug>/shape_stub.md`
11. the company-level stubs in `docs/company/`

If any file is absent, report it directly and continue with the files that are present. Do not invent repository state.

---

## 3. Source Priority and Interpretation Rules

Use this authority order when filling in information:

1. explicit user instructions in the current session;
2. repository files already present;
3. seed document founder-stated content;
4. the global Shape Catalogue;
5. clearly labelled bounded inference;
6. clearly labelled future planning.

Treat the Shape Catalogue as the primary structured source for:

- namespaces;
- categories;
- Shape IDs;
- slugs;
- names;
- kinds;
- base fields;
- relationship slots;
- payload policies;
- source-basis notes;
- `recommended_day_one_spec_order`;
- `first_declared_shape_instance_reference`;
- `day_one_repository_scaffold_policy`.

Do not flatten AccuroTech into only a software startup. Preserve the system-of-systems context, including software, communities, reporting systems, publishing, creative projects, credentialing, semantic annotation, automation, and Christian ministry/governance through WASHAD and Last Christian Church.

---

## 4. Companies / Projects to Enrich

At minimum, enrich the documentation surfaces for these slugs:

- `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`

For each project/company, inspect both seed-document sections and catalogue records whose namespace, name, slug, entry, or relationship slots appear relevant. Use exact Shape IDs where available. When no direct Shape record is available, say that the document is seed-derived and catalogue-aligned rather than catalogue-record-derived.

---

## 5. Required Per-Project Document Shape

For each `docs/projects/<project-slug>/shape_stub.md`, expand or create an informative document with this structure:

```markdown
# <Project Name> Shape Stub

**Status:** Day-Two informative scaffold, not final canon.  
**Source inputs:** ...  
**Payload safety:** ...

## Identity
- Slug:
- Names / aliases:
- Namespace(s):
- Related domains, if stated in seed documents:
- Current maturity:

## Seed Canon Summary
Summarize only what is stated in seed documents or already in repository files.

## Catalogue Alignment
List relevant Shape Catalogue namespaces, categories, Shape IDs, Shape names, kinds, base fields, relationship slots, and payload policies.

## Role in the AccuroTech Ecosystem
Explain how this project/company relates to AccuroTech and to the core triad where applicable:
- XtraType gives meaning.
- CRE8 gives authority.
- PortaShape gives structure.

## Known Fields
List known fields or concepts for this project/company.

## Missing / Unresolved Fields
List what still needs human review or future source material.

## Implementation Status
State what appears implemented, scaffolded, planned, missing, or unclear. Do not claim code works unless inspected or run.

## Day Two Build Direction
Give practical next documentation, schema, workflow, or implementation steps.

## Day Three and Beyond
List later opportunities without overbuilding now.
```

Keep these documents informative, but conservative. Prefer concise paragraphs and bullet lists over invented product copy.

---

## 6. Company-Level and Index Documents

In addition to per-project enrichment, create or update these documentation surfaces when safe:

- `docs/company/accurotech_company_shape_stub.md`
- `docs/company/values_stub.md`
- `docs/company/project_index.md`
- `docs/company/ecosystem_map.md`
- `docs/canon/day_two_catalogue_enrichment_notes.md`
- `catalogue/generated_indexes/shape_catalogue_project_alignment.md`
- `logs/boot/day_two_catalogue_enrichment_log.md`

These documents should summarize:

- the project set;
- which catalogue namespaces and Shape IDs appear relevant to each project;
- what is seed canon versus bounded inference;
- what remains unresolved;
- what should happen next.

---

## 7. Scaffold Expansion Policy

You may build out existing stubs into more useful documents, but follow these rules:

- Preserve existing useful content.
- Do not overwrite historical logs or user-authored canon without explicit instruction.
- Make small, coherent edits.
- Do not add secrets or private payloads.
- Do not create fake APIs, fake deployment status, fake customers, fake screenshots, fake package scripts, or fake production readiness.
- Do not claim implementation exists unless repository files prove it.
- Mark bounded inference explicitly.
- Prefer `Day-Two informative scaffold` language over final-canon language.
- If a document becomes long, use headings and bullets so future automation can parse it.

---

## 8. Suggested Enrichment Method

1. Inspect repository status and list available scaffold files.
2. Parse the global Shape Catalogue and build a mapping of:
   - namespace prefix to namespace name;
   - category to Shape IDs;
   - Shape ID to slug, name, kind, base fields, relationship slots, and payload policy.
3. For each project slug, find likely catalogue matches by:
   - namespace prefix;
   - project name or alias;
   - slug fragments;
   - relationship slots;
   - category summaries.
4. Extract seed-document project descriptions where present.
5. Expand each project stub using only sourced or clearly labelled inferred content.
6. Create/update the company index, ecosystem map, catalogue alignment index, and enrichment log.
7. Validate changed JSON files, if any.
8. Report exactly what changed and what remains unresolved.

---

## 9. Expected Output of a Session Running This Prompt

A successful session should produce:

- enriched per-project Shape stub documents under `docs/projects/<project-slug>/shape_stub.md`;
- company-level index and ecosystem map documents;
- catalogue-to-project alignment notes;
- a Day-Two enrichment log;
- a clear final summary that cites changed files;
- tests/checks run, especially JSON validation if JSON files are touched.

If the repository is unavailable, produce a partial in-chat plan only and say repository enrichment could not be performed.

---

## 10. Ready Statement

After completing the required reading and scaffold enrichment, state:

> Day-Two catalogue enrichment is ready for review. The scaffold has been expanded into informative documents while preserving payload safety and distinguishing seed canon, catalogue alignment, bounded inference, planned work, and implemented work.

Then ask the user which project/company should be promoted first from informative scaffold to formal canon candidate.