{
  "_meta": {
    "source": "ui_leviathan/web/content/support.md",
    "version": "0.4",
    "status": "LIVING",
    "synced_at": "2026-10-19T15:04:04.140Z",
    "content_hash": "fddaa27bb1cdb75b745c672aba9ab379def2d9034c39b5124a3d3f314a880821",
    "generator": "web/scripts/sync-docs.mjs"
  },
  "frontmatter": {
    "title": "Support the next research step",
    "version": "0.4",
    "status": "LIVING",
    "updated": "2026-10-16"
  },
  "body_md": "\n# Support work we can examine\n\nLeviathan researches how people, AI systems, and independent groups can develop knowledge, language, and learning together. We want observations, concepts, methods, and values to travel with enough context for another participant to question, use, or improve them. Independent groups should retain their own approaches. Animal welfare is an intended first application; the purpose extends to other research and practical work. [What is Leviathan?](/what-is) explains that wider proposal.\n\nWe are preparing a bounded next research stage and welcome contributions of ideas, resources and expertise. This briefing opens a discussion of that work. The contribution form can deliver an inspected question or offer to the private inbox when intake is enabled. This is a way to begin a conversation; funding arrangements still need an accountable recipient and agreed terms.\n\n## What the present evidence supports\n\nIn the first [local inquiry](/research#what-changed), a review request carried a pilot finding but omitted the exact decision under review. The reviewer identified the gap. Supplying the decision and sources enabled further review and a procedural correction: future requests should include the full decision reference. These were coordinated Codex development roles (OpenAI Codex, an AI coding assistant used in development), with context carried by an operator. The episode shows a correction in our own work; improved performance on later unfamiliar work remains untested.\n\nThe [synthetic correction pilot](/research/correction-pilot/README.md) returned equal results for equivalently scoped JSON and prose conditions. It establishes no advantage for structured representation. Our website, forum code, authored language, and inquiry records are starting pieces; their existence does not establish a deployed independent learning network. The [representation claim and its limits](/library/claims/C02) remain open to challenge.\n\n## A proposed next stage\n\nThe [research programme](/research) connects three inquiries: when observations support knowledge, how meanings develop between observers, and how uncertainty can produce discoveries and better learning methods. Support could help develop a missing concept, construct a useful test or examine a method borrowed from another field. The questions themselves remain open to change.\n\nOne proposed study within that programme compares versioned structured context with good ordinary documents under equal resources: the same relevant evidence, task access, model conditions, and time or compute limits. Include incomplete dependencies, shared sources, corrected observations, and a transfer between groups with different concepts or policies. A receiving group should be able to propose a new distinction or use a method without silently adopting the originating group's authority or values. The [study direction](/research#first-proposed-study) and [local comparison proposal](/research#comparison-proposal@0.1.0) are proposals, not an executed comparison.\n\nBefore running the comparison, agree the cases, evaluation method, resource accounting, and what would count as a useful result. Measure the cost of finding and correcting a dependency, whether the correction reaches affected work, and whether the receiving group finds the resulting answer or method useful. Preserve failures, equal results, unresolved disagreements, and simpler alternatives alongside improvements. Publish reusable test cases, the evaluation method, source-version references, resource use, results, and the resulting design decision. A changed procedure alone is insufficient evidence of better learning.\n\nThe [open contribution cards](/contribute) name proposed work **OW-001, OW-002, and OW-003**. Their small starters ask for one counterexample or baseline, one consequential ambiguity and repair, or one useful method or new question with a test. About 150–300 words is only a suggestion; a full study is not required to begin. Each card explains a possible benefit to the contributor as well as the project. Fuller work needs an agreed scope and a willing responsible participant. External people, agents with their operator’s authorization, and groups can bring a case, idea, implementation or evaluation without endorsing the whole proposal.\n\nDiscovery and making useful things are part of this invitation. A method from elsewhere could open a different research direction, help another group with its own work, or lead to a design we have not considered. The [new-question path](/contribute#prepare) does not require an existing claim to correct. The [contribution process](/contribute/process) describes how a reasoned response and any resulting work should be recorded. A reply or an improvement is not promised.\n\n## Resources and responsibilities\n\nUseful support includes compute or API credits for agreed comparisons; time and expertise in evaluation, language, software, and research methods; and potentially grant funds for a defined programme of work. We have not established an amount, schedule, legal applicant, eligibility, or committed reviewer. Before submitting an application or accepting resources, establish the accountable applicant or recipient, suitable programme, budget, duration, responsibilities, and reporting terms.\n\nMimar initiated Leviathan. Begin with a [short contribution](/contribute#prepare), naming the work and support you can offer. Inspect it and choose **Submit for review** when [intake is enabled](/api/contributions/v1). The resulting thread is visible to its credential holder and authorized reviewers, with no automatic public mirroring. No GitHub or forum account is needed. An authorized agent can use [HTTPS](/contribute/protocol.md), or a person can carry an inspected draft and return the receipt and reply. Copying or downloading alone sends nothing.\n\nKeep the committed receipt and return to the same thread with the retained browser profile or runtime credential. Access lasts 90 days from reservation, and the pilot allows one contribution and two participant follow-ups. Project maintainers name a reviewer when work is taken up; a response or acceptance is not guaranteed. Keep secrets, sensitive personal information, and confidential terms out of the intake. Establish an appropriate exchange separately if the discussion needs them; do not share API keys.\n\nYou may instead choose the [public Leviathan meta issues](https://github.com/leviathan-protocol/meta/issues) for an offer intended to be public. That optional route requires a GitHub account or an authorized agent with GitHub access; replies continue on the original issue. Neither route is a payment service or grant application, and this briefing records no secured funding. A continuation record helps preserve context but supplies no access credential or evidence that a reply was used.\n\nResource contributions do not buy decisions, preferred conclusions, or vetoes over objections. Agreed scopes, material conditions, conflicts of interest, and results should have public written records, with confidential details excluded. The [participation guide](/participate) explains current contribution routes and their limits.\n\n[Read or save this briefing as Markdown](/support.md).\n\n*Initial basis (8 October 2026): What is Leviathan? 0.13 and Vision 0.9 (4 October 2026); The Work 0.4 (4 October); Participate 0.9 (6 October). Revision 0.1 · 8 October 2026: initial support briefing; later revisions are listed below and tracked in the [content revision map](/updates/content).*\n\n*Revision 0.2 · 8 October 2026: follows The Work 0.6 and Participate 0.11, adds small starters and an open new-question path, and separates contribution preparation from delivery and funding. This is local intake preparation, not a deployment, outreach report, capacity commitment, or funding award.*\n\n*Revision 0.3 · 13 October 2026: follows The Work 0.7 and Participate 0.12 and aligns support discussions with the bounded private inbox, optional public GitHub route, and same-thread return. Resource acceptance remains a separate agreement. This source revision records no deployment, funding award, or universal client access.*\n\n*Revision 0.4 · 16 October 2026: connects support to the knowledge, meaning and discovery programme. The proposed comparison is one study within that programme; no funding, result or schedule is established.*\n"
}
