Choose a way to contribute.
Use the software, examine the research, or bring a problem where work outlasts its executor. These are independent entrances; adopting Bulla is not a prerequisite.
Try and report
Carry one coding job from the browser into a local report. Describe where the instructions or result were unclear. No Bulla installation is required.
Run and review the coding job →Share public feedback →Inspect and challenge
Reproduce an advertised result, test a claim, or identify a cheaper conventional approach. A finding remains useful when it contradicts the project.
Start with one unfinished job: examine what its successor may do, what must remain held, and what the retained account cannot establish.
Examine the successor-decision question →Describe a relevant workflow
Describe one unfinished episode from a buyer, supplier, or affected party’s perspective. Who needed to act next? What did existing systems retain, what evidence or authority was missing, and what did reconstruction cost? A conventional solution that already works is useful evidence.
Describe a workflow on GitHub →Prepare a private draft first →GitHub issues are public. Share only a description you are authorized to disclose; do not include private records, credentials, or personal data. This site currently offers no private research submission channel. Drafts prepared below stay in your browser until you choose to copy them.
Report a successor-decision finding
Describe a decision, ambiguity, or conventional alternative. No signature, Bulla installation, or qualification packet is required to report an observation.
- Case/checkpoint and material examined
- Expected and observed decision
- Supporting evidence, ambiguity, or missing information
- Minimal reproduction, if applicable
- Conventional alternative and its assumptions
- Environment, only if software was run
GitHub issues are public. Do not submit confidential records, credentials, or personal data. Share only material you are authorized to disclose.
Opening the link prepares an issue; it does not submit one.
Ordinary feedback does not automatically count as an external implementation, reliance decision, or validated result.
Prepare a workflow draft
These seven questions help identify the missing evidence or authority. Preparing a draft does not submit it. You can write a separate, non-sensitive description for a public GitHub issue.
Detailed contribution and qualification routes
01
Receipt one action in shadow mode
Add an ActionReceipt beside one existing operational log. Keep it out of production gates and settlement actions while you compare the records.
Start →02
External reliance candidate → possible D
Apply a published ReliancePolicy, sign the bulla.rely and boundary receipts, and retain the closed evidence package. Intake is open; the packet remains NOT_COUNTED until signed qualification and head records merge.
Start →03
Independent witness candidate → possible W
Run the public source-only operator kit under separate control, retain both release receipts, publish the read-only proof surface, and submit the closed candidate. A candidate never counts itself.
Start →04
Replay candidate → r
Run the frozen Python and standalone Node reports over the constructed witness fork and 10,000-decision graph. This does not create an outside witness operation.
Start →05
Prepare a cross-system disagreement
Describe how two systems or organizations use the same term differently. The browser prepares a private draft for you to keep or share.
Start →06
Challenge one claim
Test an authority, privacy, effect, or generalization claim. Findings remain publishable even when they contradict the project.
Start →07
Independent implementation → I
Implement a bounded checker from its written profile without importing Bulla.
Start →Prepare a signed candidate.
Keep the provider ActionReceipt, receiver-signed bulla.rely receipt, signed boundary receipt, organization-key attestations, control evidence, and runtime replay in one closed package. The public checker must recompute the same RELY, REFUSE, or ESCALATE outcome.
Intake is open at D0. A passing packet remains NOT_COUNTED until the dedicated intake authority signs a qualification event and ledger head and the reviewable pull request merges. The packet does not establish a later payment, deployment, or other worldly effect.
Analysis template
The review method asks for a typed claim chain, countermodel or distinction, RELY/REFUSE envelope, evidence options, burden coordinates, finality obstruction, and a replayable receipt. This page prepares the intake only; it does not submit an analysis request.
Read the review constitution →