AccuroTech Internal Shapes

Raw source view

docs/projects/solar-power-crypto/shape_stub.md

# Solar Power Crypto Shape Stub

**Status:** Day-Two informative scaffold, not final canon.
**Source inputs:** `accurotech_seed_document_v0_0_1.md`; `accurotech_seed_boot_v0_0_1.md`; global Shape Catalogue JSON; Day-One summary/log; instance record; Day-Two plan.
**Payload safety:** Metadata and documentation only; excludes private keys, live credentials, tokens, deployment secrets, private customer payloads, concrete private observations, and secret operational data.

## Identity
- Slug: `solar-power-crypto`
- Names / aliases: Solar Power Crypto
- Namespace(s): `SPC` (Solar Power Crypto knowledge/community), `CL` (Cohort Lounge community), `XT` (XtraType annotation and references), `PS` (PortaShape core model)
- Related domains, if stated in seed documents: Not separately stated in this scaffold beyond project naming and known ecosystem references.
- Current maturity: Documentation scaffold and catalogue-aligned planning surface; implementation maturity is not claimed here.

## Seed Canon Summary
- Knowledge repository/community forum project that evolved from cryptocurrency/mining interest to solar-power and decentralized-energy interests.
- Bounded inference: may benefit from annotated references, structured knowledge templates, and community access.

- Cross-ecosystem seed canon preserves the core triad: XtraType gives meaning, CRE8 gives authority, and PortaShape gives structure.
- Seed canon also says AccuroTech projects are early, built/rebuilt through iteration, generally internal-first/public-later, and not to be overclaimed as mature public production systems.

## Catalogue Alignment
Relevant catalogue namespaces and records include:
- `SPC-001` — Solar Power Crypto System (`solar_power_crypto_system`, kind `entity_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: system_name, role, knowledge_scope, community_scope, stage; relationships: uses_knowledge_record, may_use_cre8_community_access; payload: `template_base_only_no_instance_payload`).
- `SPC-002` — Knowledge Repository Record (`knowledge_repository_record`, kind `record_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: topic_slot, summary_slot, reference_slots, annotation_slots, discussion_policy; relationships: may_use_xtratype_reference, may_be_structured_by_portashape; payload: `template_base_only_no_instance_payload`).
- `SPC-003` — Community Forum Thread (`community_forum_thread`, kind `content_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: thread_topic, post_slots, participant_policy, reference_policy, moderation_state; relationships: may_use_cre8_post_base; payload: `template_base_only_no_instance_payload`).
- `CL-001` — Cohort Lounge System (`cohort_lounge_system`, kind `entity_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: system_name, role, community_scope, portal_model, stage; relationships: contains_mini_blog_portal, may_use_cre8_posting; payload: `template_base_only_no_instance_payload`).
- `CL-002` — Mini-Blog Portal (`mini_blog_portal`, kind `content_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: portal_name, topic_scope, post_policy, moderation_policy, access_policy; relationships: belongs_to_cohort_lounge_system, may_use_xtratype_annotations; payload: `template_base_only_no_instance_payload`).
- `CL-003` — Community Entry Point (`community_entry_point`, kind `pattern_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: entry_topic, audience_scope, onboarding_path, related_systems, trust_policy; relationships: may_feed_xtratype_reference_collection; payload: `template_base_only_no_instance_payload`).
- `XT-001` — XtraType System (`xtratype_system`, kind `entity_shape`; category: XtraType Annotation and Reference Meaning; fields: system_name, role, reference_scope, annotation_scope, stage; relationships: uses_cre8, uses_portashape_schema, feeds_notes_pipeline; payload: `template_base_only_no_instance_payload`).
- `XT-002` — Reference Base (`reference_base`, kind `entity_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_type, locator_slot, display_label, context_slot, resolution_policy; relationships: targeted_by_annotation, may_have_xtyp_link; payload: `template_base_only_no_instance_payload`).
- `XT-003` — Annotation Base (`annotation_base`, kind `entity_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, annotation_type, comment_slot, structured_payload_slot, metadata_slots; relationships: attaches_to_reference, may_use_shape_schema, protected_by_cre8; payload: `template_base_only_no_instance_payload`).
- `XT-004` — Text Comment Annotation (`text_comment_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, comment_text_slot, context_slot, author_slot, visibility_policy; relationships: extends_annotation_base; payload: `template_base_only_no_instance_payload`).
- `XT-005` — Highlighted Text Annotation (`highlighted_text_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, highlight_slot, comment_slot, source_context, quote_policy; relationships: extends_annotation_base; payload: `template_base_only_no_instance_payload`).
- `XT-006` — Typed Annotation (`typed_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: annotation_type, type_schema_reference, allowed_fields, validation_rule, display_rule; relationships: extends_annotation_base, defined_by_portashape; payload: `template_base_only_no_instance_payload`).
- `XT-007` — Note Annotation (`note_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, note_slot, tag_slots, collection_context, review_state; relationships: extends_typed_annotation; payload: `template_base_only_no_instance_payload`).
- `XT-008` — Claim Annotation (`claim_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, claim_text_slot, support_slots, confidence_slot, review_state; relationships: extends_typed_annotation, may_link_to_citation_annotation; payload: `template_base_only_no_instance_payload`).
- `XT-009` — Correction Annotation (`correction_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, error_summary, correction_slot, basis_slots, status; relationships: extends_typed_annotation, may_update_canon_document; payload: `template_base_only_no_instance_payload`).
- `XT-010` — Citation Annotation (`citation_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, cited_reference, support_type, excerpt_policy, relevance_note; relationships: extends_typed_annotation, supports_claim_annotation; payload: `template_base_only_no_instance_payload`).
- `XT-011` — Warning Annotation (`warning_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, warning_summary, severity_slot, evidence_slots, visibility_policy; relationships: extends_typed_annotation, may_feed_report; payload: `template_base_only_no_instance_payload`).
- `XT-012` — Question Annotation (`question_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, question_text, question_type, owner_slot, resolution_state; relationships: extends_typed_annotation, may_feed_open_question; payload: `template_base_only_no_instance_payload`).
- `XT-013` — Observation Annotation (`observation_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, observation_text, time_slot, observer_slot, evidence_slots; relationships: extends_typed_annotation, may_feed_observation_record; payload: `template_base_only_no_instance_payload`).
- `XT-014` — Definition Annotation (`definition_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, term_slot, definition_slot, scope_slot, authority_status; relationships: extends_typed_annotation, may_promote_to_canon_term; payload: `template_base_only_no_instance_payload`).
- `XT-015` — Task Note Annotation (`task_note_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, task_summary, owner_slot, status_slot, workflow_candidate; relationships: extends_typed_annotation, may_feed_bot_task_template; payload: `template_base_only_no_instance_payload`).
- `XT-016` — Report Evidence Annotation (`report_evidence_annotation`, kind `template_shape`; category: XtraType Annotation and Reference Meaning; fields: reference_target, evidence_type, evidence_summary, chain_of_context, access_policy; relationships: extends_typed_annotation, may_feed_is_bad_works_report; payload: `template_base_only_no_instance_payload`).
- `XT-017` — Reference Collection (`reference_collection`, kind `content_shape`; category: XtraType Annotation and Reference Meaning; fields: collection_name, reference_slots, purpose, curation_policy, access_policy; relationships: contains_reference_base, may_feed_shape_proposal; payload: `template_base_only_no_instance_payload`).
- `XT-018` — Shared Language Term (`shared_language_term`, kind `content_shape`; category: XtraType Annotation and Reference Meaning; fields: term, meaning_slot, scope, related_terms, canon_status; relationships: may_be_defined_by_definition_annotation, may_be_catalogued_as_shape; payload: `template_base_only_no_instance_payload`).
- `PS-BOOT-001` — Day Zero to Day One Bootstrapping Shape (`day_zero_to_day_one_bootstrapping_shape`, kind `bootstrapping_shape`; category: PortaShape Core Model; fields: shape_identity, shape_number, seed_document_set, day_zero_data_package, settings_overlay, repository_memory_model, historical_log_model, boot_prompt; relationships: 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; payload: `Shape base only; no live project state, credentials, secrets, private keys, access tokens, deployment payloads, concrete private reports, concrete posts, or non-template private instance payloads.`).
- `PS-INST-001` — Day Zero Data Package (`day_zero_data_package`, kind `data_package_shape`; category: PortaShape Core Model; fields: package_identity, target_shape, source_documents, settings_overlay, defaults, constraints, validation_status, secret_exclusion_policy; relationships: customizes_shape_base, feeds_instantiation_procedure, produces_day_one_result; payload: `template_base_only_no_instance_payload`).
- `PS-INST-002` — Day One Instantiation Result (`day_one_instantiation_result`, kind `result_shape`; category: PortaShape Core Model; fields: result_identity, source_shape, source_day_zero_package, generated_artifacts, operating_state, validation_result, next_stage_direction; relationships: conforms_to_shape_base, generated_from_day_zero_package, feeds_day_two_direction; payload: `template_base_only_no_instance_payload`).
- `PS-INST-003` — Pull-String Instantiation Procedure (`pull_string_instantiation_procedure`, kind `workflow_shape`; category: PortaShape Core Model; fields: preflight_check, settings_review, validation_step, execution_step, output_capture, post_instantiation_review; relationships: uses_day_zero_data_package, executes_shape_base, creates_day_one_result; payload: `template_base_only_no_instance_payload`).
- `PS-INST-004` — Shape Settings Overlay (`settings_overlay`, kind `configuration_shape`; category: PortaShape Core Model; fields: target_shape, setting_keys, override_values, allowed_ranges, validation_rules, precedence_policy; relationships: customizes_day_zero_data_package, parameterizes_instantiation_procedure; payload: `template_base_only_no_instance_payload`).
- `PS-001` — PortaShape System (`portashape_system`, kind `entity_shape`; category: PortaShape Core Model; fields: system_name, role, template_scope, canon_scope, adoption_stage; relationships: standardizes_shape, integrates_with_xt, integrates_with_cre8; payload: `template_base_only_no_instance_payload`).
- `PS-002` — Shape Base (`shape_base`, kind `template_shape`; category: PortaShape Core Model; fields: shape_identity, shape_kind, field_model, relationship_model, validation_model; relationships: may_have_shape_instance, may_extend_shape; payload: `template_base_only_no_instance_payload`).
- `PS-003` — Shape Instance Base (`shape_instance_base`, kind `template_shape`; category: PortaShape Core Model; fields: shape_reference, instance_identity_slot, payload_slot, validation_status, provenance_slot; relationships: conforms_to_shape_base; payload: `template_base_only_no_instance_payload`).
- `PS-004` — Stackable JSON Structure (`stackable_json_structure`, kind `data_shape`; category: PortaShape Core Model; fields: base_object, extensions, constraints, composition_rules, schema_links; relationships: used_by_shape_base; payload: `template_base_only_no_instance_payload`).
- `PS-005` — Shape Template Base (`shape_template_base`, kind `template_shape`; category: PortaShape Core Model; fields: template_name, parameter_slots, required_sections, optional_sections, validation_rules; relationships: can_generate_shape_instance; payload: `template_base_only_no_instance_payload`).
- `PS-006` — Shape Pattern Base (`shape_pattern_base`, kind `pattern_shape`; category: PortaShape Core Model; fields: pattern_name, problem_context, solution_pattern, applicable_systems, failure_boundaries; relationships: may_be_encoded_as_template; payload: `template_base_only_no_instance_payload`).

## Role in the AccuroTech Ecosystem
- XtraType gives meaning by attaching annotations, references, and shared language where this project needs semantic context.
- CRE8 gives authority by providing identity, credentials, delegated access, provenance, and permission boundaries where this project needs governed participation.
- PortaShape gives structure by defining reusable schemas, templates, workflow patterns, reports, posts, observations, tasks, or canon documents.
- This project should remain understandable as a standalone surface while also fitting into the broader AccuroTech system-of-systems.

## Known Fields
- Project slug, name/aliases, and at least one catalogue namespace alignment.
- Day-Two status as an informative scaffold rather than formal canon.
- Payload-safety exclusion requirements.
- Relationship to AccuroTech and, where applicable, to the meaning/authority/structure triad.

## Missing / Unresolved Fields
- Human-approved canonical description and launch status.
- Formal owner/steward, public domain inventory, and repository-to-service mapping.
- Exact implementation inventory, if any, outside this documentation scaffold.
- Formal schemas, API boundaries, data-retention rules, and review workflows.

## Implementation Status
- Implemented: this documentation page and catalogue alignment notes only.
- Scaffolded: project folder, Shape stub, and Day-Two planning references.
- Planned or inferred: workflows, schemas, public products, communities, automations, and integrations described as future directions unless supported by later repository evidence.
- Missing or unclear: runnable source code, deployment configuration, production readiness, active users, and operational data are not claimed by this document.

## Day Two Build Direction
- Promote the most relevant catalogue records into project-specific canon candidates.
- Identify the first safe schema or workflow artifact that can be specified without secrets or private payloads.
- Add source-basis notes for each claim so future automation can distinguish seed canon from bounded inference.
- Decide which cross-project relationships should become formal Shape relationship records.

## Day Three and Beyond
- Add formal validation rules, instance examples with synthetic data, and review workflows.
- Connect implementation repositories or modules only after they are inspected.
- Prepare public/developer documentation when the human steward confirms launch posture and payload policy.