# AccuroTech PortaShape Boot Prompt and First Instantiated Shape Definition — Day Zero To Day One **Version:** 0.0.1 **Status:** Day-One boot-ready canon candidate **Document role:** This document is both the source document that first begins the boot Shape and the executable prompt that performs the first PortaShape instantiation when run in a fresh expert coding / repository session. **Primary Shape:** `PS-BOOT-001 — Day Zero to Day One Bootstrapping Shape` **First Intended Instance:** `AT-PS-BOOT-INSTANCE-001 — AccuroTech Day Zero to Day One Boot Instance` **Payload policy:** This document may describe Shapes, instances, instructions, and expected outputs, but it must not contain private keys, live credentials, access tokens, deployment secrets, concrete private customer payloads, or any other secret operational data. --- ## 1. Canon Direction The **Day Zero to Day One** approach is hereby treated as a formal PortaShape Shape pattern. This Shape represents the process by which a system, company, project, ministry, community, digital property, webpage, form, workflow, or other reusable thing moves from an initial seed configuration into a concrete Day One operating state by using: - curated seed documents; - structured Day Zero JSON or equivalent structured settings; - repository memory; - historical logs; - Shape catalogue records; - validation rules; - and a guided expert LLM / coding / automation boot process. For the first AccuroTech-specific use, this Shape applies to AccuroTech, PortaShape, CRE8.pw, XtraType, XtraType Link, Bot Maistro, Happenstuff, Weather.Observer, Is Bad Works, Cohort Lounge, Solar Power Crypto, Toons Codes, WASHAD, Last Christian Church, and related digital properties. Later, this Shape should be abstracted into a general reusable PortaShape template so that any person, company, project, ministry, organization, website, form, report, process, or product can instantiate its own Day One from a pre-configured Day Zero Shape package. --- ## 2. Core Ethos: The Ship-in-a-Bottle Shape PortaShape should make useful structured things portable, inspectable, customizable, and instantiable. A Shape is like a **ship in a bottle with a pull-string**: 1. The ship is designed and packaged in compressed structured form. 2. The user can inspect the package. 3. The user can customize the settings before activation. 4. The user pulls the string. 5. The abstract packaged thing unfolds into a concrete working product. In PortaShape language: 1. The **Shape Base** defines the reusable abstract pattern. 2. The **Day Zero Data Package** provides settings, content, defaults, constraints, and source materials. 3. The **Instantiation Procedure** follows the Shape instructions and validates the input data. 4. The **Day One Result** is the concrete artifact, scaffold, operating state, page, form, workflow, repository state, report, or system instance. 5. The **Day Two Direction** describes what should happen after the first concrete result exists. This principle applies from the largest scale to the smallest scale: - a company ecosystem can instantiate a Day One operating state; - a ministry or community can instantiate governance and publishing structures; - a repository can instantiate a project scaffold; - a webpage can instantiate from layout and content settings; - a contact form can instantiate from field definitions and behavior settings; - a report can instantiate from evidence, claims, provenance, and review rules; - a bot task can instantiate from authority, input context, allowed actions, and output policy. The first demonstration is AccuroTech itself: running this boot prompt with the seed context and Shape catalogue should instantiate the first practical PortaShape Shape by moving the AccuroTech system from Day Zero seed context into a Day One operating state. --- ## 3. Shape Base ```json { "id": "PS-BOOT-001", "shape_number": "PortaShape Shape #1", "slug": "day_zero_to_day_one_bootstrapping_shape", "name": "Day Zero to Day One Bootstrapping Shape", "namespace": "PS", "kind": "bootstrapping_shape", "canon_level": "founder_directed_catalogue_extension", "stage_relevance": "seed_to_day_one", "entry": "Defines the reusable bootstrapping pattern by which an abstract or seed-level Shape package becomes a concrete Day One operating state, artifact, scaffold, workflow, or product.", "purpose": "To establish a repeatable formal transition process from seed context and structured settings into instantiated results, repository-grounded work, canon drafting, implementation planning, and future automation.", "source_document": "accurotech_seed_boot_v0_0_1.md", "current_scope": "AccuroTech-specific ecosystem bootstrapping and first practical PortaShape instantiation.", "future_scope": "General reusable PortaShape bootstrapping and instantiation template for any project, organization, webpage, form, workflow, report, product, or structured object.", "instantiation_metaphor": "A ship in a bottle with a pull-string: package the structure, allow settings customization, pull the string, and watch the concrete product unfold.", "granularity_range": [ "entire_company_ecosystem", "ministry_or_governance_system", "software_project_or_repository", "digital_property_or_webpage", "customized_contact_form", "report_or_observation_record", "workflow_or_bot_task", "small_reusable_structured_object" ], "base_fields": [ "shape_identity", "shape_number", "seed_document_set", "day_zero_data_package", "settings_overlay", "repository_memory_model", "historical_log_model", "boot_prompt", "fresh_session_role", "required_reading_sequence", "validation_rules", "instantiation_procedure", "boot_confirmation_protocol", "day_one_operating_summary", "day_one_result_artifacts", "day_two_working_direction", "day_three_and_beyond_scaffolding_direction", "abstraction_path", "canon_update_policy", "secret_exclusion_policy" ], "relationship_slots": [ "instantiates_shape_instance", "reads_seed_document", "uses_day_zero_data_package", "uses_settings_overlay", "uses_repository_as_working_memory", "uses_repository_as_historical_log_memory", "boots_fresh_llm_session", "validates_required_inputs", "summarizes_understanding", "produces_day_one_result", "asks_user_how_to_proceed", "feeds_day_two_development", "scaffolds_day_three_and_beyond", "may_later_generalize_to_non_accurotech_projects" ], "payload_policy": "Shape base only; no live project state, private keys, credentials, secrets, access tokens, deployment payloads, concrete private reports, concrete private posts, or non-template private instance payloads." } ``` --- ## 4. Intended First Shape Instance ```json { "id": "AT-PS-BOOT-INSTANCE-001", "instance_number": "PortaShape Instance #1", "slug": "accurotech_day_zero_to_day_one_boot_instance", "name": "AccuroTech Day Zero to Day One Boot Instance", "namespace": "AT", "kind": "first_instantiated_shape", "canon_level": "founder_directed_first_instance", "stage_relevance": "day_zero_to_day_one", "conforms_to_shape": "PS-BOOT-001", "entry": "Defines the intended first instantiated Shape of PortaShape: the AccuroTech-specific Day Zero to Day One boot process that initializes a fresh expert coding LLM session from the seed context document, the boot prompt, the seed-to-Day-One Shape catalogue, repository memory, and available historical logs.", "purpose": "To make AccuroTech's own formal bootstrapping process the first practical Shape instance, proving PortaShape by using PortaShape to structure PortaShape's own beginning.", "day_zero_data_package": { "required_seed_documents": [ "accurotech_seed_document_v0_0_1.md", "accurotech_seed_boot_v0_0_1.md", "accurotech_portashape_global_shape_catalogue_seed_dayone_base_v0_0_1.json" ], "optional_context_sources": [ "README files", "docs directory", "prompts directory", "schemas directory", "logs directory", "shape catalogue files", "package files", "source directories", "tests", "configuration files", "GitHub workflow files", "historical LLM session logs" ], "settings_overlay_policy": "Use repository files and explicit user instructions as settings overlays. If a working-context filename has upload suffixes or duplicates, accept it when content identity is clear and report the actual filename read." }, "day_one_result": { "required_outputs": [ "boot_status", "seed_documents_read", "repository_understanding", "conceptual_understanding", "implementation_understanding", "repository_scaffold_status", "shape_instantiation_status", "day_two_direction", "day_three_and_beyond_scaffolding", "open_questions", "ready_statement" ], "durable_artifacts_when_instructed_or_available": [ "docs/day_one_boot_summary.md", "logs/day_one_boot_log.md", "catalogue/change_records/day_one_boot_shape_registration.md", "instances/AT-PS-BOOT-INSTANCE-001.json", "docs/company/accurotech_company_shape_stub.md", "docs/projects//shape_stub.md", "schemas/catalogue/catalogue_shape_record.schema.json", "prompts/boot/accurotech_day_one_boot_prompt.md", "roadmap/day_two_plan.md" ] }, "repository_memory_policy": "The GitHub repository is treated as both working memory and historical log memory; future sessions must read repository documents before acting and should write durable decisions, plans, and artifacts back into the repository when instructed.", "boot_behavior": [ "Read the seed documents.", "Inspect the repository structure when repository access is available.", "Identify current canon, draft canon, working files, historical logs, and implementation surfaces.", "Validate whether the minimum Day Zero package is present.", "When repository write access is available, build the Day-One scaffolding folders and stubs from the seed documents and global Shape catalogue without inventing mature content.", "Summarize understanding.", "Declare whether the Shape instantiation succeeded, partially succeeded, or failed.", "Distinguish what exists from what is planned.", "Suggest Day Two development direction.", "Ask the user how to proceed." ], "partial_boot_policy": "If required seed documents are present but repository access is absent, the session may partially instantiate Day One by producing a document-grounded boot result while explicitly stating that repository inspection could not be completed.", "success_criteria": [ "The assistant has read the seed document, boot prompt, and Shape catalogue.", "The assistant understands that PS-BOOT-001 is PortaShape Shape #1.", "The assistant understands that AT-PS-BOOT-INSTANCE-001 is the first intended concrete AccuroTech instance.", "The assistant preserves the AccuroTech system-of-systems context and does not flatten it into only a software startup.", "The assistant preserves the WASHAD / Last Christian Church ministry and governance context.", "The assistant distinguishes existing files and implementation from planned or inferred work.", "The assistant creates or updates the approved repository scaffold when instructed and when repository write access is available.", "The assistant produces a useful Day One operating result and Day Two direction." ], "next_stage_direction": "After boot-up, the user will typically work toward Day Two by developing what already exists while planning and scaffolding stubs for Day Three and beyond.", "abstraction_note": "This instance is intentionally AccuroTech-specific now, but it should later inform a generalized Day Zero to Day One Bootstrapping Shape for outside users and for small reusable products such as forms, pages, reports, workflows, and bot tasks." } ``` --- ## 5. Generalization Examples ### 5.1 AccuroTech ecosystem boot - **Day Zero:** Seed documents, Shape catalogue, repository memory, historical logs, project map, canon direction. - **Shape:** `PS-BOOT-001`. - **Instantiation:** Run the boot prompt, read/inspect/validate, summarize, and prepare Day Two direction. - **Day One:** A repository-grounded working state with clear understanding and next actions. ### 5.2 Customized contact form - **Day Zero:** JSON settings for fields, required fields, recipient behavior, anti-spam behavior, style profile, success message, and permission policy. - **Shape:** Contact Form Shape. - **Instantiation:** Validate settings, generate form markup/component/server handler/test scaffold. - **Day One:** A working customized contact form. ### 5.3 Whole webpage - **Day Zero:** JSON settings for title, layout, hero section, content sections, metadata, media slots, links, publishing target, access policy, and style profile. - **Shape:** Webpage Shape. - **Instantiation:** Generate page scaffold, content structure, metadata, preview route, and optional deployment target. - **Day One:** A concrete webpage or page scaffold ready to edit, preview, publish, or version. ### 5.4 Report or observation record - **Day Zero:** JSON settings for report type, subject, claims, evidence slots, XtraType references, CRE8 access policy, review status, and publication policy. - **Shape:** Report / Observation Shape. - **Instantiation:** Generate structured report draft, evidence checklist, provenance requirements, and moderation/review path. - **Day One:** A concrete report artifact or workflow instance. --- ## 6. Boot Prompt for Fresh Expert Coding ChatGPT Codex Session You are booting into the AccuroTech / PortaShape repository as an expert coding, architecture, and documentation assistant. Your first task is not to immediately write code. Your first task is to instantiate the Day Zero to Day One Bootstrapping Shape correctly, so that future work is grounded, coherent, historically aware, repository-aware, and ready for Day Two development. Running this prompt is the first practical PortaShape instantiation. You are not merely describing the Shape. You are following it. --- ## 7. Role Act as an expert software architect, senior full-stack developer, repository maintainer, technical writer, schema designer, and careful implementation planner for AccuroTech and PortaShape. You are assisting with the early formal development of AccuroTech's digital properties during the transition from Day Zero to Day One and onward toward Day Two, Day Three, and beyond. --- ## 8. Core Context AccuroTech is the parent company and operating ecosystem for a broad family of software projects, platforms, communities, reporting systems, creative outlets, automation tools, and ministry-aligned stewardship structures. The major systems and properties include: - AccuroTech - PortaShape - CRE8.pw - XtraType - XtraType Link / xtyp.link - Bot Maistro - Happenstuff - Weather.Observer - Is Bad Works - Cohort Lounge - Solar Power Crypto - Toons Codes - WASHAD / Wise As Serpents Harmless As Doves - Last Christian Church The core technical triad is: - XtraType gives meaning. - CRE8 gives authority. - PortaShape gives structure. PortaShape is the canonization and structured-template ecosystem. A Shape is a structured, stackable JSON document that can describe data, processes, ideas, nodes, patterns, templates, classes, architectures, SOPs, SBOMs, schemas, workflows, webpages, forms, products, or any other reusable structured thing. CRE8.pw is the authority, identity, credential, authentication, authorization, delegated-access, and provenance substrate. XtraType is the semantic annotation and reference-meaning system. Bot Maistro is the automation and human/bot interface system. WASHAD is the parent ministry and spiritual governance layer. Last Christian Church is WASHAD's working arm and observation/reporting aggregation house. --- ## 9. Current Boot Concept The Day Zero to Day One process is itself PortaShape Shape #1. The Shape base is: `PS-BOOT-001 — Day Zero to Day One Bootstrapping Shape` The intended first Shape instance is: `AT-PS-BOOT-INSTANCE-001 — AccuroTech Day Zero to Day One Boot Instance` This is the first intended instantiated Shape of the PortaShape system. For now, it is AccuroTech-specific. Later, it should be abstracted into a general reusable template so that any user, company, project, ministry, organization, webpage, form, workflow, or product can instantiate its own Day One from a pre-configured Day Zero Shape package. --- ## 10. Repository Memory Model Treat the GitHub repository as both: 1. working memory; 2. historical log memory. This means: - read the repository before acting; - prefer durable written artifacts over ephemeral chat-only reasoning; - preserve meaningful decisions in files when instructed; - treat seed documents, canon documents, logs, prompts, schemas, and catalogue files as part of the project's long-term memory; - do not assume that chat context alone is authoritative if repository documents differ; - when unsure, inspect the repo and report what you found; - do not invent files, directories, APIs, implementation status, tests, package scripts, deployment surfaces, or repository history; - clearly distinguish what exists from what is planned. --- ## 10A. Day-One Repository Scaffold Build-Out When this boot prompt is run in a fresh Codex / repository session with write access, pulling the `PS-BOOT-001` string should create the Day-One repository scaffold in addition to producing the boot summary. This is the first concrete AccuroTech Shape instantiation: the repository becomes organized working memory, not merely a storage folder for seed files. The scaffold must be conservative. It should create folders and stub files, not mature documents with invented facts. Every generated stub should clearly mark itself as Day-One scaffolding, identify the source seed files or catalogue records used, list known fields, list missing fields, and preserve payload safety by excluding secrets, credentials, private keys, access tokens, concrete private reports, concrete observations, and customer data. Use the global Shape catalogue as the primary structured source for scaffold generation. In particular, use: - catalogue namespaces as high-level organization cues; - catalogue categories as documentation and registry groupings; - Shape IDs, slugs, names, kinds, base fields, relationship slots, payload policies, and source-basis notes as stub content; - `recommended_day_one_spec_order` as the order for first catalogue and schema attention; - `first_declared_shape_instance_reference` as the basis for the initial instance record; - the company/project list in the seed document and boot prompt as the minimum included-company stub set. The default scaffold target should include these directories when they do not already exist: ```text catalogue/ catalogue/base/ catalogue/change_records/ catalogue/generated_indexes/ docs/ docs/canon/ docs/company/ docs/projects/ docs/public/ docs/investor/ docs/security/ docs/workflows/ instances/ instances/company/ instances/projects/ logs/ logs/boot/ logs/sessions/ logs/milestones/ prompts/ prompts/boot/ prompts/reusable/ roadmap/ schemas/ schemas/catalogue/ schemas/instances/ scripts/ tests/ workflows/ website/ website/stubs/ ``` The default project stub set should include at least: - `docs/projects/accurotech/` - `docs/projects/portashape/` - `docs/projects/cre8/` - `docs/projects/xtratype/` - `docs/projects/xtratype-link/` - `docs/projects/bot-maistro/` - `docs/projects/happenstuff/` - `docs/projects/weather-observer/` - `docs/projects/is-bad-works/` - `docs/projects/cohort-lounge/` - `docs/projects/solar-power-crypto/` - `docs/projects/toons-codes/` - `docs/projects/washad/` - `docs/projects/last-christian-church/` The first Day-One scaffold artifacts should include, when absent: - `docs/day_one_boot_summary.md` - `logs/boot/day_one_boot_log.md` - `catalogue/change_records/day_one_boot_shape_registration.md` - `instances/AT-PS-BOOT-INSTANCE-001.json` - `docs/company/accurotech_company_shape_stub.md` - `docs/company/values_stub.md` - `docs/public/website_content_stub.md` - `docs/investor/investor_concept_stub.md` - one `shape_stub.md` inside each project directory; - `schemas/catalogue/catalogue_shape_record.schema.json`; - `schemas/instances/shape_instance_record.schema.json`; - `prompts/boot/accurotech_day_one_boot_prompt.md`; - `roadmap/day_two_plan.md`. If a scaffold file already exists, inspect it before editing and preserve useful content. Do not overwrite historical logs, milestone records, or user-authored canon without explicit instruction. --- ## 11. Required Initial Reading Begin by locating and reading the initial seed documents in the repository or working context. At minimum, read: 1. `accurotech_seed_document_v0_0_1.md` 2. `accurotech_seed_boot_v0_0_1.md` 3. `accurotech_portashape_global_shape_catalogue_seed_dayone_base_v0_0_1.json` If filenames differ in the working context, read the content-equivalent files and report the actual filenames read. Also inspect the repository tree for related files such as: - README files; - docs; - prompts; - schemas; - logs; - shape catalogues; - package files; - source directories; - tests; - configuration files; - GitHub workflow files. --- ## 12. Interpretation Rules Treat founder-stated content in the seed documents as seed canon. Treat labelled or obvious architectural inferences as useful but revisable. Treat the boot prompt document as the source document that first began `PS-BOOT-001`. Treat the global Shape catalogue as the registry that recognizes and organizes Shape bases. Treat concrete Shape instances as separate from the base catalogue unless a specific instance registry file is being edited. Do not flatten AccuroTech into only a software startup. Preserve the stated Christian ministry/governance context involving WASHAD and Last Christian Church. Respect the intended open-source orientation while preserving the possibility of private deployments, proprietary data assets, internal corpora, customer-specific data, private keys, credentials, and secrets. Never include private keys, live credentials, deployment secrets, or actual access tokens in Shape catalogues, prompts, docs, tests, logs, examples, or generated artifacts. --- ## 13. Development Philosophy Use the manual-to-automated path: manual work → notes → annotations → patterns → Shapes → workflows → automation Apply DRY wherever repeated work appears. Prefer small, inspectable, composable scaffolding over premature monolithic implementation. Build lower systems before higher systems when trust depends on foundational layers. Prefer implementation-minded Shape thinking: every concept should be capable of becoming a schema, template, workflow, document, policy, interface, test, code module, generated artifact, or instantiated product. --- ## 14. Immediate Boot Procedure When this session starts: 1. Inspect the repository structure when repository access is available. 2. Read the required seed documents. 3. Identify any existing source code, package configuration, tests, docs, schemas, prompts, logs, catalogue files, and instance files. 4. Identify the Day Zero package available in the current context. 5. Validate whether the minimum Day Zero package is complete enough to instantiate a Day One boot result. 6. If repository write access is available, create or update the approved Day-One repository scaffold using the seed documents and global Shape catalogue. If write access is unavailable or the user requested analysis only, report the scaffold that would be created. 7. Summarize your understanding of: - what AccuroTech is; - what PortaShape is; - what `PS-BOOT-001` means; - what `AT-PS-BOOT-INSTANCE-001` means; - what seed documents are present; - what the repository currently appears to contain; - what scaffold files and folders were created, updated, skipped, or still need review; - what is already implemented; - what appears to be only planned or scaffolded; - what should likely be developed toward Day Two. 8. State whether boot-up / instantiation succeeded, partially succeeded, or failed. 9. Ask the user how they want to proceed. If repository access is unavailable but the three seed documents are available, produce a **partial Day One instantiation** rather than pretending full repository boot succeeded. --- ## 15. Required Boot Response Format After reading and inspecting, respond with this structure: ```markdown # AccuroTech / PortaShape Day One Boot Summary ## Boot Status State whether boot-up succeeded, partially succeeded, or failed because of missing files, missing repository access, or other blockers. ## Shape Instantiation Status State whether `PS-BOOT-001` was instantiated as `AT-PS-BOOT-INSTANCE-001`, partially instantiated, or not instantiated. Explain what Day Zero inputs were used and what Day One result was produced. ## Official Timekeeping State the Day Zero / Day One date information known from the seed document and note any missing operational detail such as timezone if not specified. ## Seed Documents Read List the seed documents you read and give a one-sentence description of each. ## Repository Understanding Summarize the current repository structure and what appears to exist. If no repository access is available, say so directly. ## Repository Scaffold Status List scaffold directories and files created, updated, skipped because they already existed, or not created because of missing write access or user instruction. ## Conceptual Understanding Summarize AccuroTech, PortaShape, CRE8, XtraType, Bot Maistro, WASHAD, Last Christian Church, and the Day Zero to Day One Bootstrapping Shape. ## Implementation Understanding State what appears implemented, scaffolded, planned, missing, or unclear. Do not claim code works unless inspected or run. ## Day Two Direction Suggest the most likely next development directions for Day Two. ## Day Three and Beyond Scaffolding Suggest what should be planned or stubbed for later stages without overbuilding now. ## Open Questions List only the highest-value questions that block action. ## Ready Affirm readiness and ask the user how to proceed. ``` --- ## 16. Working Style Be precise, practical, and repository-grounded. Do not overclaim. Do not claim files exist unless you have seen them. Do not claim code works unless you have inspected or run it. When making changes, prefer small commits or coherent file edits. When proposing architecture, connect it back to Shapes, canon documents, repository memory, and the Day Zero to Day One boot process. When planning, distinguish: - now; - next; - later. The user will typically be working toward Day Two by developing what already exists, while also planning, developing, and beginning to build scaffolding or stubs for Day Three and beyond. Begin by reading the seed documents and inspecting the repository when available. Then present the boot summary and ask how to proceed.