AccuroTech Internal Shapes

Raw source view

docs/projects/cohort-lounge/shape_stub.md

# Cohort Lounge 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: `cohort-lounge`
- Names / aliases: Cohort Lounge
- Namespace(s): `CL` (Cohort Lounge community), `CRE8` (CRE8 authority, credential, and access), `XT` (XtraType annotation and references), `PS` (PortaShape core model), `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
- Casual community-facing gathering place and possible host for mini-blog portals.
- Bounded inference: softer public square for the ecosystem.

- 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:
- `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`).
- `CRE8-001` — CRE8.pw System (`cre8_system`, kind `entity_shape`; category: CRE8 Authority, Credential, and Access; fields: system_name, role, authority_scope, access_scope, development_stage; relationships: protects_project_system, underlies_xtratype; payload: `template_base_only_no_instance_payload`).
- `CRE8-002` — Owner Account (`owner_account`, kind `entity_shape`; category: CRE8 Authority, Credential, and Access; fields: account_identity, root_authority_slot, community_model, monitoring_policy, delegation_scope; relationships: mints_key, governs_credential_hierarchy; payload: `template_base_only_no_instance_payload`).
- `CRE8-003` — Credential Hierarchy (`credential_hierarchy`, kind `relationship_shape`; category: CRE8 Authority, Credential, and Access; fields: root_credential, child_credentials, authority_path, permission_inheritance, revocation_path; relationships: contains_cre8_key, supports_lineage_verification; payload: `template_base_only_no_instance_payload`).
- `CRE8-004` — CRE8 Key Base (`cre8_key_base`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: key_id_slot, key_type, issuer_slot, permission_set, status; relationships: has_four_key_bundle, belongs_to_credential_hierarchy; payload: `template_base_only_no_instance_payload`).
- `CRE8-005` — Primary Author Key (`primary_author_key`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: authority_scope, minting_permissions, post_permissions, delegation_permissions, audit_requirement; relationships: extends_cre8_key_base, may_mint_author_key; payload: `template_base_only_no_instance_payload`).
- `CRE8-006` — Secondary Author Key (`secondary_author_key`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: authority_scope, allowed_minting, forbidden_minting, post_permissions, scope_boundary; relationships: extends_cre8_key_base, bounded_by_no_primary_escalation; payload: `template_base_only_no_instance_payload`).
- `CRE8-007` — Use Key (`use_key`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: access_scope, resource_scope, interaction_permissions, expiration_policy, revocation_policy; relationships: extends_cre8_key_base, grants_resource_access; payload: `template_base_only_no_instance_payload`).
- `CRE8-008` — Keychain (`keychain`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: keychain_mode, member_slots, content_slots, update_policy, revocation_policy; relationships: contains_use_key, may_attach_to_post; payload: `template_base_only_no_instance_payload`).
- `CRE8-009` — Four-Key Credential Bundle (`four_key_credential_bundle`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: system_public_key_slot, system_private_key_slot, utility_public_key_slot, utility_private_key_slot, separation_policy; relationships: belongs_to_cre8_key_base; payload: `template_base_only_no_instance_payload`).
- `CRE8-010` — System Keypair (`system_keypair`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: public_key_slot, private_key_slot, allowed_signatures, authority_scope, protection_policy; relationships: part_of_four_key_bundle, signs_authority_event; payload: `template_base_only_no_instance_payload`).
- `CRE8-011` — Utility Keypair (`utility_keypair`, kind `credential_shape`; category: CRE8 Authority, Credential, and Access; fields: public_key_slot, private_key_slot, allowed_uses, rotation_policy, exposure_policy; relationships: part_of_four_key_bundle, receives_access_envelope; payload: `template_base_only_no_instance_payload`).
- `CRE8-012` — CRE8 Post Base (`post_base`, kind `content_shape`; category: CRE8 Authority, Credential, and Access; fields: author_slot, category_slot, tag_slots, access_grant_slots, provenance_slot; relationships: created_by_author_key, protected_by_access_grant; payload: `template_base_only_no_instance_payload`).
- `CRE8-013` — Access Grant (`access_grant`, kind `permission_shape`; category: CRE8 Authority, Credential, and Access; fields: grantor_slot, grantee_slot, resource_scope, permission_scope, revocation_rule; relationships: applies_to_post, may_be_attached_to_keychain; payload: `template_base_only_no_instance_payload`).
- `CRE8-014` — Permission Set (`permission_set`, kind `permission_shape`; category: CRE8 Authority, Credential, and Access; fields: allowed_actions, denied_actions, inheritance_rule, delegation_rule, scope_boundary; relationships: attached_to_cre8_key_base; payload: `template_base_only_no_instance_payload`).
- `CRE8-015` — Provenance Chain (`provenance_chain`, kind `record_shape`; category: CRE8 Authority, Credential, and Access; fields: event_sequence, issuer_links, signature_links, affected_resources, verification_status; relationships: built_from_authority_event, supports_accountability; payload: `template_base_only_no_instance_payload`).
- `CRE8-016` — Authority Event (`authority_event`, kind `event_shape`; category: CRE8 Authority, Credential, and Access; fields: event_type, actor_credential, target_resource, signature_slot, effective_policy; relationships: signed_by_system_keypair, adds_to_provenance_chain; payload: `template_base_only_no_instance_payload`).
- `CRE8-017` — Revocation Event (`revocation_event`, kind `event_shape`; category: CRE8 Authority, Credential, and Access; fields: revoked_subject, revoker_slot, reason_slot, scope, effective_rule; relationships: updates_provenance_chain, affects_access_grant; payload: `template_base_only_no_instance_payload`).
- `CRE8-018` — Pseudonymity with Accountability Policy (`pseudonymity_accountability_policy`, kind `policy_shape`; category: CRE8 Authority, Credential, and Access; fields: public_identity_policy, internal_accountability_policy, lineage_requirement, moderation_scope, privacy_boundary; relationships: governs_owner_account, governs_use_key; payload: `template_base_only_no_instance_payload`).
- `CRE8-019` — Blast-Radius Control (`blast_radius_control`, kind `policy_shape`; category: CRE8 Authority, Credential, and Access; fields: problem_signal, affected_scope, containment_action, review_rule, restoration_path; relationships: uses_revocation_event, uses_permission_reduction; payload: `template_base_only_no_instance_payload`).
- `CRE8-020` — Access Envelope (`access_envelope`, kind `data_shape`; category: CRE8 Authority, Credential, and Access; fields: recipient_key_slot, resource_reference, encrypted_material_slot, usage_policy, expiration_policy; relationships: encrypted_to_utility_keypair, unlocks_protected_resource; 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`).

## 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.