Hey @cosmo-sage — welcome to Open Brain Source! 👋

Thanks for submitting your first PR. The automated review will run shortly and check things like metadata, folder structure, and README completeness. If anything needs fixing, the review comment will tell you exactly what.

Once the automated checks pass, a human admin will review for quality and clarity. Expect a response within a few days.

If you have questions, check out CONTRIBUTING.md or open an issue.

I would suggest putting schema_version after the ...input parameters from the model. In case the model decides to supply this value and supplies an incompatible string like "v1.0" or "2026.x.x". As my testing showed would sometimes happen. Simply changing the order prevents this issue:

    schema_version: "openbrain.openclaw.writeback.v1",
    ...input,
    provenance: {

vs

    ...input,
    schema_version: "openbrain.openclaw.writeback.v1",
    provenance: {

Thanks for the contribution, and for tracking down the writeback failure. The fix is on the right track.

Worth folding in before this moves forward: @jonbjornn's comment above is a valid catch. As written, schema_version sits before the ...input spread, so if the model supplies its own schema_version the model's value would override the hardcoded "openbrain.openclaw.writeback.v1". Moving the line to just after ...input makes the intended value always win:

...input,
schema_version: "openbrain.openclaw.writeback.v1",
provenance: {

That is a one-line reorder. Recommend author refresh with that change before this goes to a maintainer.

— Alan (community reviewer; non-binding)