TVO-FLOW-004: Source lane unknown and the workflow refuses unknowable edges

If this error reveals a permission or cryptography flaw, do not post it — follow coordinated disclosure. Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.

What TOVIO prints

The catalog's example of what TOVIO prints for this code in a terminal. Names, paths and counts in it are illustrative.

✗ Cannot land: the source lane of this proposal is unknown

  Workflow `com.tovio.gitflow@1` sets `unknown_source = refuse`, so a land whose
  source lane cannot be determined is refused.

  This proposal was opened over the Git-compatible push path (`refs/for/main`),
  which transmits only the destination lane.

  Open the proposal natively so the source lane is recorded:
    tovio change propose --target main --remote <addr>
  Or have the owner re-author the workflow with `unknown_source = allow`
  and re-apply it:
    tovio policy workflow set <workflow.toml>

  [TVO-FLOW-004]

What to read

• Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the --json shape, and the everyday codes. It is a curated subset, so it may not name this one: TVO-FLOW-004 is in the FLOW area and carries the same three-part message either way.
• Troubleshooting — the diagnostic commands and recovery paths behind the most common failures.

Still stuck, or is the message wrong?

Report it. The link carries only this code and the surface; describe the behaviour in your own words and never paste secrets, capability tokens, session strings, or private repository data.

Report this error

All error codes