Raw source view
docs/projects/bot-maistro/shape_stub.md
# Bot Maistro 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: `bot-maistro` - Names / aliases: Bot Maistro - Namespace(s): `BM` (Bot Maistro automation), `WF` (Operating workflow and philosophy), `SEC` (Security, provenance, and trust), `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 - Human/bot interface and automation coordination layer for bots, agents, delegated tasks, workflows, and human-supervised activity. - Bounded inference in seed canon says delegated bot authority likely needs scoped permissions, provenance, auditability, and revocation. - 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: - `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`). - `WF-001` — Iteration and Rebuild Pattern (`iteration_rebuild_pattern`, kind `pattern_shape`; category: Operating Philosophy and Build Workflow; fields: iteration_context, rebuild_reason, retained_knowledge, replacement_target, lesson_capture; relationships: feeds_canon_document, feeds_shape_revision; payload: `template_base_only_no_instance_payload`). - `WF-002` — Living Architecture (`living_architecture`, kind `architecture_shape`; category: Operating Philosophy and Build Workflow; fields: current_state, change_drivers, stability_boundary, review_cadence, open_questions; relationships: qualifies_project_system, updates_shape_family; payload: `template_base_only_no_instance_payload`). - `WF-003` — Manual-to-Automated Spectrum (`manual_to_automated_spectrum`, kind `workflow_shape`; category: Operating Philosophy and Build Workflow; fields: manual_step, standardization_step, template_step, automation_step, quality_goal; relationships: implemented_by_portashape, coordinated_by_bot_maistro; payload: `template_base_only_no_instance_payload`). - `WF-004` — DRY Repetition Capture (`dry_repetition_capture`, kind `policy_shape`; category: Operating Philosophy and Build Workflow; fields: repetition_signal, capture_method, template_candidate, automation_candidate, review_rule; relationships: feeds_shape_proposal, feeds_workflow_template; payload: `template_base_only_no_instance_payload`). - `WF-005` — Lower System Enables Higher System (`lower_system_enables_higher_system`, kind `pattern_shape`; category: Operating Philosophy and Build Workflow; fields: lower_system, enabled_capability, trust_requirement, dependency_boundary, maturity_signal; relationships: orders_implementation_priority; payload: `template_base_only_no_instance_payload`). - `WF-006` — Structured Knowledge Pipeline (`structured_knowledge_pipeline`, kind `workflow_shape`; category: Operating Philosophy and Build Workflow; fields: raw_input, annotation_step, pattern_extraction, shape_creation, automation_readiness; relationships: uses_xtratype, uses_portashape, feeds_bot_maistro; payload: `template_base_only_no_instance_payload`). - `WF-007` — Expected Reliable Automation (`expected_reliable_automation`, kind `policy_shape`; category: Operating Philosophy and Build Workflow; fields: expected_result, system_boundary, validation_method, failure_mode, human_review_rule; relationships: governs_automation_workflow; payload: `template_base_only_no_instance_payload`). - `WF-008` — Seed-to-Day-One Build Stage (`seed_to_day_one_build_stage`, kind `stage_shape`; category: Operating Philosophy and Build Workflow; fields: stage_name, primary_objective, allowed_outputs, excluded_outputs, next_stage_signal; relationships: applies_to_catalogue, applies_to_project_system; payload: `template_base_only_no_instance_payload`). - `WF-009` — Now / Next / Later Stage Model (`now_next_later_stage_model`, kind `stage_shape`; category: Operating Philosophy and Build Workflow; fields: now_scope, next_scope, later_scope, promotion_criteria, risks; relationships: applies_to_project_system, feeds_release_roadmap; payload: `template_base_only_no_instance_payload`). - `WF-010` — Implementation-Minded Shape Thinking (`implementation_minded_shape_thinking`, kind `pattern_shape`; category: Operating Philosophy and Build Workflow; fields: concept_name, implementation_surface, required_fields, validation_needed, automation_path; relationships: guides_shape_record; payload: `template_base_only_no_instance_payload`). - `SEC-001` — Credentialed Authority (`credentialed_authority`, kind `security_shape`; category: Security, Provenance, and Trust Components; fields: credential_reference, authority_scope, delegation_chain, verification_rule, revocation_rule; relationships: implemented_by_cre8; payload: `template_base_only_no_instance_payload`). - `SEC-002` — Delegated Access (`delegated_access`, kind `security_shape`; category: Security, Provenance, and Trust Components; fields: delegator, delegatee, resource_scope, action_scope, duration_rule; relationships: may_use_cre8_access_grant; payload: `template_base_only_no_instance_payload`). - `SEC-003` — Authentication Base (`authentication_base`, kind `security_shape`; category: Security, Provenance, and Trust Components; fields: subject_slot, auth_method, verification_state, session_policy, failure_policy; relationships: implemented_by_cre8; payload: `template_base_only_no_instance_payload`). - `SEC-004` — Authorization Base (`authorization_base`, kind `security_shape`; category: Security, Provenance, and Trust Components; fields: subject_slot, resource_slot, action_slot, permission_source, decision_result; relationships: implemented_by_cre8_permission_set; payload: `template_base_only_no_instance_payload`). - `SEC-005` — Audit Record Base (`audit_record_base`, kind `record_shape`; category: Security, Provenance, and Trust Components; fields: actor_slot, action_slot, target_slot, time_slot, verification_slot; relationships: may_extend_provenance_chain; payload: `template_base_only_no_instance_payload`). - `SEC-006` — Trust Boundary (`trust_boundary`, kind `policy_shape`; category: Security, Provenance, and Trust Components; fields: boundary_name, trusted_inputs, untrusted_inputs, allowed_actions, escalation_rule; relationships: governs_automation_workflow, governs_report_workflow; payload: `template_base_only_no_instance_payload`). - `SEC-007` — Private-Key Exposure Reduction (`private_key_exposure_reduction`, kind `policy_shape`; category: Security, Provenance, and Trust Components; fields: protected_key_type, routine_key_type, exposure_rule, rotation_rule, exception_policy; relationships: implemented_by_four_key_credential_bundle; payload: `template_base_only_no_instance_payload`). - `SEC-008` — Encrypted Resource Sharing (`encrypted_resource_sharing`, kind `security_shape`; category: Security, Provenance, and Trust Components; fields: resource_reference, recipient_key, encrypted_material_slot, decryption_policy, revocation_consideration; relationships: uses_utility_keypair, may_use_access_envelope; payload: `template_base_only_no_instance_payload`). - `SEC-009` — High-Confidence Provenance (`high_confidence_provenance`, kind `security_shape`; category: Security, Provenance, and Trust Components; fields: source_actor, signature_chain, lineage_path, verification_state, confidence_notes; relationships: uses_system_keypair, supports_canon_review; payload: `template_base_only_no_instance_payload`). - `SEC-010` — Containment Action (`containment_action`, kind `event_shape`; category: Security, Provenance, and Trust Components; fields: action_type, target_scope, authority_source, reason_slot, review_state; relationships: may_create_revocation_event, implements_blast_radius_control; 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`). ## 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.