Log inGet started
What it does

zeromind.contribute

Send improvements to installed content back upstream — git subtree push ending in a pull request.

When you improve an asset you installed from another world, zeromind.contribute sends the change to the world that owns it. For each targeted origin world the diverging subtree is remapped to the origin's canonical paths, three-way merged against the origin's current content, pushed as a contrib-<id> branch in the origin world, and opened as a pull request there.

If the origin changed the same content in the meantime, those regions come back as local conflicts with markers written into your files. Resolve them the same way you resolve a pull conflict, then run zeromind.contribute again.

By default each pull request is merged immediately when you have write access to the origin (otherwise it is left open for review), and the local fork re-syncs so the contributed asset reads as level with its origin again rather than perpetually ahead.

Discover what is ahead first with zeromind.forkStatus. Pass targets to contribute to a subset of origins, merge = false to open the pull requests without merging, or dryRun = true to see the plan without pushing anything.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

This asset doesn't declare a schema or structured payload.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

0items
Assets0Files0
This part has no composite children. See the Files segment for its leaf payloads.
This part has no leaf payloads.

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.