Skip to content

grok crm: schema and canonical ids #13456

Open

Description

@gHashTag

Schema for the unified CRM: entities, states, and one canonical id per actor. See #13455.

Boundary

  • specs/automation/grok_crm.t27 :: fn id_ok

User Scenarios

Given two actor ids when they are compared then a duplicate canonical id is refused.

Requirements

  • FR-001: Every actor id MUST match 0xRole@domain.t27.
  • FR-002: Person, company, deal, task, and mail states MUST stay inside their declared ranges.

Success Criteria

  • exit 0 from typecheck.
  • 1 test covers id_ok.

Activity

  1. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec created: specs/automation/grok_crm_schema.t27 (typecheck OK, 1 test pass).

  2. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.

  3. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Specs created for M10 milestone. Typecheck OK.

  4. gHashTag commented on Nov 18, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions