Reader-mode pilot: Limen audience editions and evidence record

[4444J99]

Summary

Pilots the Class A reader-mode contract on Limen, separating general, technical, humanities, business, and evaluator routes while preserving the canonical positioning record.

Truth boundaries

• canonical repository: 4444J99/limen; former organvm/limen identity recorded
• status is active/public with explicit operational boundaries
• no “zero ops,” zero-maintenance, or unbounded self-healing claim
• industry mappings are labeled proposed inferences with dedicated evidence
• conduct, verification, persona, licensing, and deployment claims are auditable

Contract dependencies

• editorial standard #12
• canonical schema #16
• validation runtime #174

Verification

• strict schema/runtime validation passed
• actual checkout identity binding passed
• git-tracked evidence gate passed
• assertion semantics and local evidence hashes passed
• changed-file links and git diff --check passed

Pre-merge metadata blocker

GitHub About still advertises “Zero ops,” retains a zero-ops topic, and points its homepage at a former identity. Those settings cannot be corrected through this PR and must be updated directly before merge.

Summary by Sourcery

Establish an evidence-bounded reader-mode documentation and project-record layer for Limen, with audience-specific routes and explicit boundaries around deployment, authorship, adoption, and licensing.

New Features:

• Add audience-specific reader-mode documentation for general, technical, humanities, business, and evaluator readers.
• Add a canonical project record and machine-readable evidence assertions and receipts for Limen's status, capabilities, authorship, deployment, and limitations.

Bug Fixes:

• Correct project positioning to remove unsupported zero-operations and open-source claims, identify the canonical repository, and distinguish historical evidence from current status.

Enhancements:

• Reframe the README around bounded multi-agent governance, inspectable completion evidence, audience routes, operational status, and explicit limitations.
• Document the conduct lifecycle, authority boundaries, persona-separated disclosure, proposed applications, failure modes, and evaluation paths across the new audience editions.
• Extend governance manifests to register audience documentation and the canonical project record.

Documentation:

• Replace the outdated README positioning with evidence-bounded project documentation and links to public status, technical material, and evidence records.

Chores:

• Record unresolved licensing, adoption, reliability, and comparative-performance boundaries in the canonical project metadata.

[sourcery-ai]

Reviewer's Guide

This PR pilots Limen's Class A reader-mode contract by replacing broad product positioning with audience-specific documentation backed by a canonical project record, machine-readable evidence assertions, dated receipts, and explicit boundaries around deployment, adoption, authorship, licensing, and proposed industry use.

Sequence diagram for bounded Limen work and evidence-bearing completion

sequenceDiagram
    participant Requester
    participant Client
    participant Keeper as TABVLARIVS_keeper
    participant Executor
    participant Evidence
    Requester->>Client: submit_work_packet
    Client->>Keeper: submit_graph
    Keeper->>Keeper: lease_resource
    Keeper-->>Executor: claim_lease
    Executor->>Executor: execute_bounded_work
    Executor->>Keeper: report
    Keeper->>Evidence: validate_receipt
    Evidence-->>Keeper: predicate_evidence
    Keeper-->>Client: terminal_lifecycle_state

Loading

Flow diagram for Limen claim boundaries

flowchart LR
    I["Inspectable implementation"] --> C["Claim ledger"]
    D["Dated runtime receipts"] --> C
    C --> V["Verified capability or deployment"]
    C --> P["Proposed application"]
    C --> U["Unknown adoption"]
    C --> X["Contradicted license claim"]
    V --> L["Published with explicit limitations"]
    P --> L
    U --> L
    X --> L

Loading

File-Level Changes

Change	Details	Files
Reframes the repository landing page around a canonical project record and bounded reader-mode claims.	Replaces the former product pitch with a concise system description and audience navigation. Adds explicit operational status, evidence boundaries, limitations, authorship disclosure, and unresolved licensing status. Updates the task lifecycle explanation to emphasize keeper-owned state, leases, authority, budgets, and terminal evidence. Removes the MIT/open-source assertion until a license file is committed.	README.md
Adds audience-specific documentation routes for general, technical, humanities, business, and evaluator readers.	Explains Limen's purpose, workflow, architecture, interfaces, failure modes, and verification paths at different levels of technical depth. Separates implemented capabilities from proposed applications, internal operation, deployment observations, and unsupported adoption or outcome claims. Documents authority, memory, authorship, delegated labor, operational risks, integration requirements, and responsible pilot questions.	docs/audiences/general.md docs/audiences/technical.md docs/audiences/humanities.md docs/audiences/business.md docs/audiences/evaluator.md
Introduces a machine-readable canonical project record for shared factual claims and audience routing.	Records repository identity, active/public status, authorship, implementation scope, limitations, concepts, links, and audience editions. Centralizes claim postures and references to assertion evidence instead of duplicating machine-readable claims. Labels industry applications as proposed and adoption as unknown.	project-record.yml
Adds an evidence ledger and machine-readable assertion and receipt records to make positioning claims auditable.	Maps implementation, persona, deployment, internal-operation, authorship, licensing, verification, adoption, and proposed-industry claims to evidence. Adds dated public endpoint and repository receipts plus freshness guidance distinguishing historical metrics from current observations. Documents claim withdrawal and boundary rules for stale or unsupported evidence.	docs/positioning/evidence/limen.md docs/positioning/evidence/assertions/adoption-boundary.json docs/positioning/evidence/assertions/authorship.json docs/positioning/evidence/assertions/conduct-contract.json docs/positioning/evidence/assertions/internal-operation.json docs/positioning/evidence/assertions/license-status.json docs/positioning/evidence/assertions/persona-surfaces.json docs/positioning/evidence/assertions/proposed-industry-applications.json docs/positioning/evidence/assertions/public-deployment.json docs/positioning/evidence/assertions/verification-rails.json docs/positioning/evidence/receipts/github-repository-2026-08-31.json docs/positioning/evidence/receipts/public-endpoints-2026-08-31.json
Registers the new reader-mode documentation and project record with repository governance manifests.	Sanctions the audience documentation directory. Adds project-record.yml as the canonical documentation registry consumed by reader routes and README content. Normalizes the manifest ending with a newline.	institutio/governance/docs-manifest.yaml institutio/governance/root-manifest.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}