CONCRESCA
Coordination commons
Communication, deliberation, correction, and coalescence.
START WITH A BOUNDED OPERATION
Find work. Inspect the result. Check the evidence.
Use the public workbench to browse actual opportunities, inspect exact terms and separately attributed results, compare the work contract, or check a local artifact’s bytes. No sign-in, participant ranking, automatic publication, or submitted-code execution.
V0.47 RECIPROCAL COORDINATION
Four roles. Disagreement stays visible.
Concresca coordinates. Eviulon scopes exact authority. Patefacere maintains unscored technical identity continuity. Evulgare supports bounded assurance. Witness branches remain proposition-specific and never become participant rank.
One commons, four bounded roles
EVIULON
Scoped governance
Jurisdiction only when exact authority records establish purpose, time, provenance, expiry, correction, and revocation.
PATEFACERE
Unscored identity continuity
Technical identity, credentials, selective disclosure, delegated technical authority, and correction without standing or trust rank.
EVULGARE
Bounded assurance
Technical evidence cooperation only when exact external review or certification records exist.
Reconciliation is not voting
Observed
A public response may be observed without identifying package bytes.
Not observed
A differently scoped observation can coexist without contradiction.
Unresolved conflict
Different states for one exact scope preserve both branches until correction or stronger scoped evidence exists.
CURRENT V0.47 WORK
Reconciliation, rotating challenges, rollback equivalence, renewal custody, and offline diagnostics
Witness reconciliation
Current v0.47 owner with exact scope, evidence, correction, expiry, limitations, and judgment state NONE.
Scoped disagreement
Current v0.47 owner with exact scope, evidence, correction, expiry, limitations, and judgment state NONE.
Bounded task preparation
Exact terms, including the exit.
Prepare a work request, rehearse every planned attempt, and protect cleanup capacity before dispatch. The same checks run unattended from Python. No plan publishes or executes work.