AccuroTech Internal Shapes

Raw source view

docs/projects/toons-codes/shape_stub.md

# Toons Codes 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: `toons-codes`
- Names / aliases: Toons Codes
- Namespace(s): `TOON` (Toons Codes creative outlet), `BM` (Bot Maistro automation), `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
- Creative outlet/studio for creative coding, cartoons, visual experiments, playful software, stories, media, and milestone comics.
- Seed canon links Toons.Codes and Bot Maistro to comic strips generated for major milestone steps or session history logs.

- 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:
- `TOON-001` — Toons Codes System (`toons_codes_system`, kind `entity_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: system_name, role, creative_scope, input_sources, stage; relationships: receives_milestone_trigger, publishes_creative_artifact; payload: `template_base_only_no_instance_payload`).
- `TOON-002` — Creative Artifact Template (`creative_artifact_template`, kind `creative_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: artifact_type, source_context, creative_brief, asset_slots, publication_policy; relationships: may_be_generated_from_session_log; payload: `template_base_only_no_instance_payload`).
- `TOON-003` — Milestone Comic Template (`milestone_comic_template`, kind `creative_shape`; category: Publishing, Community, Knowledge, and Creative Properties; fields: milestone_reference, story_summary, panel_count_rule, caption_policy, approval_state; relationships: triggered_by_milestone_creative_trigger; payload: `template_base_only_no_instance_payload`).
- `BM-001` — Bot Maistro System (`bot_maistro_system`, kind `entity_shape`; category: Bot Maistro Automation and Delegated Work; fields: system_name, role, automation_scope, delegation_scope, stage; relationships: uses_cre8_authority, uses_portashape_task_template, uses_xtratype_context; payload: `template_base_only_no_instance_payload`).
- `BM-002` — Human/Bot Interface (`human_bot_interface`, kind `interface_shape`; category: Bot Maistro Automation and Delegated Work; fields: human_actor_slot, bot_actor_slot, interaction_mode, approval_policy, audit_policy; relationships: mediates_bot_task, uses_cre8_permissions; payload: `template_base_only_no_instance_payload`).
- `BM-003` — Bot Actor Base (`bot_actor_base`, kind `entity_shape`; category: Bot Maistro Automation and Delegated Work; fields: bot_identity, authority_scope, task_scope, supervision_rule, revocation_rule; relationships: authorized_by_cre8_key, performs_bot_task; payload: `template_base_only_no_instance_payload`).
- `BM-004` — Delegated Bot Authority (`delegated_bot_authority`, kind `permission_shape`; category: Bot Maistro Automation and Delegated Work; fields: delegator_slot, bot_actor, allowed_actions, boundaries, expiration_policy; relationships: implemented_by_cre8_access_grant; payload: `template_base_only_no_instance_payload`).
- `BM-005` — Bot Task Template (`bot_task_template`, kind `template_shape`; category: Bot Maistro Automation and Delegated Work; fields: task_name, input_context_slots, allowed_actions, expected_output, review_rule; relationships: may_use_xtratype_reference, requires_cre8_authority; payload: `template_base_only_no_instance_payload`).
- `BM-006` — Automation Workflow Base (`automation_workflow_base`, kind `workflow_shape`; category: Bot Maistro Automation and Delegated Work; fields: workflow_name, trigger, steps, authority_requirements, success_criteria; relationships: composed_of_bot_task_template, may_be_triggered_by_event; payload: `template_base_only_no_instance_payload`).
- `BM-007` — Human-Supervised Activity (`human_supervised_activity`, kind `workflow_shape`; category: Bot Maistro Automation and Delegated Work; fields: activity_type, supervisor_slot, review_points, rollback_policy, audit_record; relationships: wraps_automation_workflow_base; payload: `template_base_only_no_instance_payload`).
- `BM-008` — Automation Audit Record (`automation_audit_record`, kind `record_shape`; category: Bot Maistro Automation and Delegated Work; fields: actor_slot, action_summary, inputs_used, outputs_created, review_status; relationships: records_bot_task, feeds_provenance_chain; payload: `template_base_only_no_instance_payload`).
- `BM-009` — History Log Automation (`history_log_automation`, kind `workflow_shape`; category: Bot Maistro Automation and Delegated Work; fields: source_session, naming_rule, storage_target, indexing_rule, review_rule; relationships: automates_time_indexed_folder_pattern, creates_session_log; payload: `template_base_only_no_instance_payload`).
- `BM-010` — Milestone Creative Trigger (`milestone_creative_trigger`, kind `automation_shape`; category: Bot Maistro Automation and Delegated Work; fields: trigger_event, source_material, creative_target, approval_rule, output_reference; relationships: feeds_toons_codes_artifact; 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`).
- `DOC-009` — Indexed Discovery Record (`indexed_discovery_record`, kind `record_shape`; category: Documents, Notes, Logs, and Source Materials; fields: item_reference, index_terms, content_type, related_shapes, discovery_status; relationships: indexes_raw_source_document, may_use_xtyp_link; payload: `template_base_only_no_instance_payload`).
- `DOC-010` — Notes-to-Canon Workflow (`notes_to_canon_workflow`, kind `workflow_shape`; category: Documents, Notes, Logs, and Source Materials; fields: note_sources, annotation_step, synthesis_step, review_step, canon_output; relationships: uses_xtratype, uses_portashape, creates_canon_document; payload: `template_base_only_no_instance_payload`).
- `REL-001` — Core Triad Relationship (`core_triad_relationship`, kind `relationship_shape`; category: Cross-System Integration and Data Pipelines; fields: meaning_system, authority_system, structure_system, integration_goal, reuse_policy; relationships: links_xtratype_cre8_portashape; payload: `template_base_only_no_instance_payload`).
- `REL-002` — Reference-Meaning-Authority-Structure Pipeline (`reference_meaning_authority_structure_pipeline`, kind `workflow_shape`; category: Cross-System Integration and Data Pipelines; fields: reference_step, meaning_step, authority_step, structure_step, automation_step; relationships: uses_xtratype, uses_cre8, uses_portashape; payload: `template_base_only_no_instance_payload`).
- `REL-003` — CRE8 Protects Project (`cre8_protects_project`, kind `relationship_shape`; category: Cross-System Integration and Data Pipelines; fields: protected_system, credential_scope, access_model, provenance_requirement, stage; relationships: source_cre8_system, target_project_system; payload: `template_base_only_no_instance_payload`).
- `REL-004` — XtraType Annotates Project (`xtratype_annotates_project`, kind `relationship_shape`; category: Cross-System Integration and Data Pipelines; fields: target_system, reference_types, annotation_types, visibility_policy, shape_schema_policy; relationships: source_xtratype_system, target_project_system; payload: `template_base_only_no_instance_payload`).
- `REL-005` — PortaShape Structures Project (`portashape_structures_project`, kind `relationship_shape`; category: Cross-System Integration and Data Pipelines; fields: target_system, shape_families, template_scope, validation_policy, canon_status; relationships: source_portashape_system, target_project_system; payload: `template_base_only_no_instance_payload`).
- `REL-006` — Weather-to-Happenstuff Pipeline (`weather_to_happenstuff_pipeline`, kind `workflow_shape`; category: Cross-System Integration and Data Pipelines; fields: weather_observation, publication_target, annotation_policy, access_policy, review_rule; relationships: source_weather_observer, target_happenstuff; payload: `template_base_only_no_instance_payload`).
- `REL-007` — Report-to-Stewardship Pipeline (`report_to_stewardship_pipeline`, kind `workflow_shape`; category: Cross-System Integration and Data Pipelines; fields: source_report, evidence_bundle, aggregation_target, review_rule, stewardship_context; relationships: source_is_bad_works, target_last_christian_church; payload: `template_base_only_no_instance_payload`).
- `REL-008` — Bot Task Context Pipeline (`bot_task_context_pipeline`, kind `workflow_shape`; category: Cross-System Integration and Data Pipelines; fields: task_template, authority_grant, reference_context, expected_output, audit_record; relationships: uses_bot_maistro, uses_cre8, uses_xtratype, uses_portashape; payload: `template_base_only_no_instance_payload`).
- `REL-009` — Creative Milestone Pipeline (`creative_milestone_pipeline`, kind `workflow_shape`; category: Cross-System Integration and Data Pipelines; fields: milestone_record, session_history, creative_trigger, artifact_template, publication_policy; relationships: source_doc_milestone, target_toons_codes; payload: `template_base_only_no_instance_payload`).
- `REL-010` — Catalogue-to-Repository Pipeline (`catalogue_to_repository_pipeline`, kind `workflow_shape`; category: Cross-System Integration and Data Pipelines; fields: shape_record, repository_target, schema_output, documentation_output, release_stage; relationships: may_publish_to_github, uses_open_source_orientation; 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.