Source Evidence Dataset Development

Use this top-level skill when there is no import-ready LCA package and the task must develop or update TIDAS rows from evidence.

Managed Foundry tasks

When the caller supplies a registered public Foundry task and its current result, use this skill as a domain helper. Retrieve and assess source evidence, or prepare the current requested evidence-backed decision or patch input. Keep the supplied workspace, task, actor and account intent. Return newly authored input files through the current public semantic/action contract and let Foundry register and validate them.

Use the current task brief and only the applicable registered decisions supplied by the caller. Keep a user's requirement, an AI assumption and each source fact distinct; a user choice does not fill a scientific evidence gap or grant a write. Return a material conflict or missing fact to the ordinary Foundry entry with its effect, supporting evidence and precise question or next investigation. This managed-task guidance does not change the independent seed and queue procedure below.

Advance the task only through its supplied structured next_actions, preserving executable, argv, CWD and binding. Do not run the standalone queue procedure below inside that task, overwrite registered rows or reports, write checkpoint.json yourself, or recreate a task after an uncertain write. Follow the original task's readback/recovery action. Task and account permission remain bound to the existing scope.

foundry-tidas-import is the ordinary entry for starting and continuing managed Foundry work. This helper can consume a supplied task result without requiring another skill directory to be installed. The remaining procedure applies to an independent CLI workflow whose state is outside the managed public task protocol.

Boundaries