Skip to content

[P1] Establish PMF and integration evidence before adapter-marketplace investment #39

Description

@chaoz23

Problem

There is no demonstrated external usage, integration, adapter adoption, retention, support demand, or willingness to pay. The repository currently proves a thesis and kernel, not a market.

Acceptance criteria

  • Recruit at least three independent AI-DM/VTT design partners.
  • Track installation-to-first-verdict, repeat use, supported/refused calls, and integration effort.
  • Run problem and willingness-to-pay interviews separate from solution demos.
  • Define investment and kill thresholds before major coverage or marketplace work.
  • Defer adapter marketplace and voice/video expansion until integration pull is demonstrated.

Activity

  1. chaoz23 commented on Aug 2, 2026

    @chaoz23
    OwnerAuthor

    Concrete integration evidence is now available in draft PRs #60 and
    chaoz23/table-kit#14.

    PR #60 projects srdcheck's existing scoped legal/illegal/refusal contract into
    table.evaluation/1.0 without changing native or MCP behavior. Table-kit #14
    pins that exact commit, builds/cold-installs both wheels outside their source
    checkouts, and validates six result paths against the installed shared schema
    and semantic rules. The gate explicitly preserves the distinction between a
    failed saving throw (a completed adjudication) and an illegal action (a finding
    with exact rule/citation evidence), while missing facts, unsupported content,
    and invalid input remain non-clean.

    All srdcheck hosted matrices are green (Python 3.10–3.13, minimum runtime,
    Windows/macOS, cold install/artifact), and the table-kit hosted srdcheck gate is
    green. Both PRs remain draft and unreleased; this is integration proof, not PMF
    or observed-table evidence.

  2. chaoz23 commented on Aug 2, 2026

    @chaoz23
    OwnerAuthor

    Concrete integration evidence is now available in draft PRs #60 and
    chaoz23/table-kit#14.

    Current immutable heads, superseding the earlier pre-rebase evidence, are
    21a43d8c2a6791465be9e0fb9856ce05888292d0 for srdcheck #60 and
    7cf2d0f51b9248bb050d88b56eee7c88816a1135 for table-kit #14. The former is
    based directly on current srdcheck main after merged #59 and #61.

    PR #60 projects srdcheck's existing scoped legal/illegal/refusal contract into
    table.evaluation/1.0 without changing native or MCP behavior. Table-kit #14
    pins that exact commit, builds/cold-installs both wheels outside their source
    checkouts, and validates six result paths against the installed shared schema
    and semantic rules. The gate explicitly preserves the distinction between a
    failed saving throw (a completed adjudication) and an illegal action (a finding
    with exact rule/citation evidence), while missing facts, unsupported content,
    and invalid input remain non-clean.

    All srdcheck hosted matrices are green (Python 3.10–3.13, minimum runtime,
    Windows/macOS, cold install/artifact), and the table-kit hosted srdcheck gate is
    green. Both PRs remain draft and unreleased; this is integration proof, not PMF
    or observed-table evidence.

  3. chaoz23 commented on Aug 2, 2026

    @chaoz23
    OwnerAuthor

    Concrete integration evidence is now available in draft PRs #60 and
    chaoz23/table-kit#14.

    Current immutable heads, superseding the earlier pre-rebase evidence, are
    4bb87ee31f69f0dd70f6ceb176392c97b3147f33 for srdcheck #60 and
    e7433f9b2686b3f2409cfe01e3fb5bf0d62544d0 for table-kit #14. The former is
    based directly on current srdcheck main after merged #59 and #61.

    PR #60 projects srdcheck's existing scoped legal/illegal/refusal contract into
    table.evaluation/1.0 without changing native or MCP behavior. Table-kit #14
    pins that exact commit, builds/cold-installs both wheels outside their source
    checkouts, and validates six result paths against the installed shared schema
    and semantic rules. The gate explicitly preserves the distinction between a
    failed saving throw (a completed adjudication) and an illegal action (a finding
    with exact rule/citation evidence), while missing facts, unsupported content,
    and invalid input remain non-clean.

    All srdcheck hosted matrices are green (Python 3.10–3.13, minimum runtime,
    Windows/macOS, cold install/artifact), and the table-kit hosted srdcheck gate is
    green. Both PRs remain draft and unreleased; this is integration proof, not PMF
    or observed-table evidence.

  4. chaoz23 commented on Aug 2, 2026

    @chaoz23
    OwnerAuthor

    Concrete integration evidence is now available in draft PRs #60 and
    chaoz23/table-kit#14.

    Current immutable heads, superseding the earlier pre-rebase evidence, are
    4bb87ee31f69f0dd70f6ceb176392c97b3147f33 for srdcheck #60 and
    442be1b5f4ecc5fb3f31c5966831174cbf630258 for table-kit #14. The former is
    based directly on current srdcheck main after merged #59 and #61.

    PR #60 projects srdcheck's existing scoped legal/illegal/refusal contract into
    table.evaluation/1.0 without changing native or MCP behavior. Table-kit #14
    pins that exact commit, builds/cold-installs both wheels outside their source
    checkouts, and validates six result paths against the installed shared schema
    and semantic rules. The gate explicitly preserves the distinction between a
    failed saving throw (a completed adjudication) and an illegal action (a finding
    with exact rule/citation evidence), while missing facts, unsupported content,
    and invalid input remain non-clean.

    All srdcheck hosted matrices are green (Python 3.10–3.13, minimum runtime,
    Windows/macOS, cold install/artifact), and the table-kit hosted srdcheck gate is
    green. Both PRs remain draft and unreleased; this is integration proof, not PMF
    or observed-table evidence.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions