eva-link

Tell Eva you want to customize a Link and describe your workflow. The Builder interviews you about the scenario, collects 3-5 real samples for expression-type Links, produces a definition card for confirmation, then generates eva.link.json, module.md, and test files.

Use the Link Doctor by asking Eva to check or diagnose your Link. It runs strict validation on the config, module file, asset handoff declarations, and registry fingerprints, then reports blockers, risks, and the shortest fix path.

No. Links whose id or entry aliases collide with core entry points are blocked from mounting. When both a Link and a core module could handle a request, the core module takes priority unless you explicitly name the Link.

By default a Link can only read the current input, declared upstream assets, and its own package files. Networking, writing files, and saving user data are disabled unless you explicitly authorize them after reviewing a plain-language permission summary.

The registry stores an approved SHA-256 fingerprint covering both eva.link.json and module.md. Any change to either file invalidates the fingerprint, so the Link must be re-reviewed and re-confirmed before it can run again.

Do not use a Link for ordinary one-off writing like a single Moments post or article; those go through Eva's standard creation pipeline. Links are only for workflows you explicitly want to reuse and invoke by name or confirmed default.