8000 Add collaboration-first upstream contribution workflow for established Lean libraries · Issue #69 · Mnehmos/MathOS · GitHub
[go: up one dir, main page]

Skip to content

Add collaboration-first upstream contribution workflow for established Lean libraries #69

Open

Description

@Mnehmos

Goal

Encode the collaboration pattern requested by Statlib: discuss the target first, agree on sources and generality, then produce one small reviewable contribution rather than submitting a generated whole-paper development.

Proposed workflow

proposed
→ community_discussion
→ scope_agreed
→ source_grounded
→ implementation
→ kernel_verified
→ fidelity_review
→ review_ready
→ upstream_pr
→ upstreamed | revision_requested | rejected

Required records

  • target upstream repository and module;
  • discussion URL, issue, or Zulip thread;
  • proposed reviewer or maintainer contact;
  • canonical source and exact anchors;
  • declaration and dependency blueprint;
  • agreed level of generality;
  • first-PR boundary;
  • unresolved semantic questions;
  • AI/tool disclosure;
  • proof-search provenance;
  • upstream issue/PR and review outcome.

Repository separation

Support explicit lanes:

reusable_library/
  source-grounded, reviewed, general infrastructure

campaigns/
  paper-specific, experimental, or frontier formalizations

Reusable library code may be promoted out of a campaign through this workflow. Campaign code must not silently become trusted shared infrastructure.

Initial vertical

Use foundational multiple-testing infrastructure as the first Statlib integration candidate:

  • hypotheses and decisions;
  • rejection sets;
  • false positives and false negatives;
  • false discovery proportion and false discovery rate;
  • multiple-testing procedures;
  • Benjamini–Hochberg procedure and basic properties.

The exact first task remains subject to Statlib maintainer agreement.

Acceptance criteria

  • MathOS can create and track an upstream contribution from discussion through merge.
  • Implementation cannot begin in approved upstream mode without an agreed source and PR boundary.
  • Exports generate a concise contribution packet for Zulip/GitHub review.
  • The first fixture demonstrates extracting one small reusable unit from a larger campaign.
  • Upstream review feedback is preserved as structured evidence and can trigger repair cycles.

Activity

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

      0