AccuroTech Internal Shapes

Raw source view

docs/projects/portashape/shape_stub.md

# PortaShape 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: `portashape`
- Names / aliases: PortaShape
- Namespace(s): `PS` (PortaShape core model), `META` (Catalogue and canon infrastructure), `DOC` (Documents, notes, and logs), `REL` (Cross-system relationships and data pipelines)
- 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
- Central meta-system for reusable structured JSON Shapes, templates, schemas, processes, canonization, and pull-string instantiation.
- It is complementary to XtraType and CRE8: meaning, authority, and structure.

- 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:
- `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`).
- `PS-007` — Canonization Workflow (`canonization_workflow`, kind `workflow_shape`; category: PortaShape Core Model; fields: candidate_source, proposal_step, review_step, approval_step, revision_step; relationships: creates_shape_record, updates_canon_status; payload: `template_base_only_no_instance_payload`).
- `PS-008` — Shape Validation Rule (`shape_validation_rule`, kind `policy_shape`; category: PortaShape Core Model; fields: rule_id, target_field, constraint_type, severity, message; relationships: applies_to_shape_base, applies_to_shape_instance; payload: `template_base_only_no_instance_payload`).
- `PS-009` — Shape Relationship Base (`shape_relationship_base`, kind `relationship_shape`; category: PortaShape Core Model; fields: relationship_type, source_shape, target_shape, cardinality, constraint; relationships: links_shape_records; payload: `template_base_only_no_instance_payload`).
- `PS-010` — Shape Permission Profile (`shape_permission_profile`, kind `permission_shape`; category: PortaShape Core Model; fields: view_policy, edit_policy, approval_policy, instantiation_policy, publication_policy; relationships: may_use_cre8_permission_bundle; payload: `template_base_only_no_instance_payload`).
- `PS-011` — Public Community Shape (`public_community_shape`, kind `template_shape`; category: PortaShape Core Model; fields: community_domain, template_type, sharing_policy, attribution_policy, version_policy; relationships: may_be_submitted_by_user, may_be_curated_by_portashape; payload: `template_base_only_no_instance_payload`).
- `PS-012` — Proprietary Shape Asset (`proprietary_shape_asset`, kind `data_shape`; category: PortaShape Core Model; fields: asset_scope, owner_context, access_policy, storage_policy, public_metadata_policy; relationships: protected_by_cre8, conforms_to_shape_base; payload: `template_base_only_no_instance_payload`).
- `META-001` — Shape Catalogue (`shape_catalogue`, kind `catalogue_shape`; category: Catalogue and Canon Infrastructure; fields: catalogue_id, title, version, stage, namespaces, categories, shape_records; relationships: contains_shape_family, references_source_document; payload: `template_base_only_no_instance_payload`).
- `META-002` — Shape Record (`shape_record`, kind `record_shape`; category: Catalogue and Canon Infrastructure; fields: id, slug, name, namespace, kind, canon_level, entry, base_fields; relationships: belongs_to_category, may_extend_shape; payload: `template_base_only_no_instance_payload`).
- `META-003` — Shape Namespace (`shape_namespace`, kind `namespace_shape`; category: Catalogue and Canon Infrastructure; fields: prefix, name, domain_scope, owning_system, description; relationships: contains_shape_records; payload: `template_base_only_no_instance_payload`).
- `META-004` — Canon Status (`canon_status`, kind `status_shape`; category: Catalogue and Canon Infrastructure; fields: status_code, label, definition, approval_requirement, change_policy; relationships: applies_to_shape_record; payload: `template_base_only_no_instance_payload`).
- `META-005` — Source Basis (`source_basis`, kind `source_shape`; category: Catalogue and Canon Infrastructure; fields: basis_type, source_reference, confidence, notes, review_status; relationships: supports_shape_record, may_reference_document; payload: `template_base_only_no_instance_payload`).
- `META-006` — Bounded Inference Marker (`bounded_inference_marker`, kind `marker_shape`; category: Catalogue and Canon Infrastructure; fields: inference_summary, basis, boundary, review_needed, promotion_path; relationships: qualifies_shape_record; payload: `template_base_only_no_instance_payload`).
- `META-007` — Shape Version (`shape_version`, kind `version_shape`; category: Catalogue and Canon Infrastructure; fields: major, minor, patch, revision_note, effective_stage; relationships: versions_shape_record, feeds_change_history; payload: `template_base_only_no_instance_payload`).
- `META-008` — Shape Change Record (`shape_change_record`, kind `change_record_shape`; category: Catalogue and Canon Infrastructure; fields: change_type, changed_fields, reason, reviewer, timestamp_policy; relationships: updates_shape_version, references_source_basis; payload: `template_base_only_no_instance_payload`).
- `META-009` — Shape Family (`shape_family`, kind `family_shape`; category: Catalogue and Canon Infrastructure; fields: family_id, name, namespace, summary, member_shape_ids, priority; relationships: contains_shape_records, depends_on_shape_family; payload: `template_base_only_no_instance_payload`).
- `META-010` — Global Shape Catalogue Stage (`global_shape_catalogue_stage`, kind `stage_shape`; category: Catalogue and Canon Infrastructure; fields: stage_code, stage_name, entry_criteria, exit_criteria, allowed_use; relationships: applies_to_catalogue; payload: `template_base_only_no_instance_payload`).
- `DOC-001` — Seed Context Document (`seed_context_document`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: document_title, purpose, authority_level, scope, continuation_instruction; relationships: anchors_source_basis, feeds_shape_catalogue; payload: `template_base_only_no_instance_payload`).
- `DOC-002` — Canon Document (`canon_document`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: title, canon_scope, approved_content_slots, effective_date_rule, revision_history; relationships: may_define_shape, may_be_cited_by_shape_record; payload: `template_base_only_no_instance_payload`).
- `DOC-003` — Official Description (`official_description`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: subject, short_description, long_description, audience, status; relationships: may_be_embedded_in_shape_record; payload: `template_base_only_no_instance_payload`).
- `DOC-004` — SOP Document (`sop_document`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: procedure_name, purpose, steps, roles, quality_checks; relationships: derived_from_notes, may_be_shape_template; payload: `template_base_only_no_instance_payload`).
- `DOC-005` — Raw Source Document (`raw_source_document`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: source_type, origin, content_scope, indexing_state, conversion_candidate; relationships: may_feed_xtratype_annotation, may_feed_shape_proposal; payload: `template_base_only_no_instance_payload`).
- `DOC-006` — LLM Conversation Log (`llm_conversation_log`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: session_reference, participants, topic_scope, extractable_items, review_status; relationships: may_feed_session_history, may_feed_shape_catalogue; payload: `template_base_only_no_instance_payload`).
- `DOC-007` — Session History Log (`session_history_log`, kind `document_shape`; category: Documents, Notes, Logs, and Source Materials; fields: session_time_record, context_summary, decisions, outputs, next_actions; relationships: may_trigger_milestone_creative_trigger; payload: `template_base_only_no_instance_payload`).
- `DOC-008` — Milestone Record (`milestone_record`, kind `event_shape`; category: Documents, Notes, Logs, and Source Materials; fields: milestone_name, scope, source_evidence, impact_summary, followup_work; relationships: may_create_session_history_comic, updates_project_history; 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.