tiangong-lca Foundry TIDAS Authoring
Use this internal, on-demand role for an existing Foundry semantic work item. Ordinary import or source-evidence execution enters through TianGong Foundry. This role authors data files; Foundry owns task state, validation, deterministic apply, authorization and execution.
Read the current work item
Read the task JSON/Markdown, its authoring package, action items, target rows, source evidence and referenced dependency/identity reports. Read the shared context bundle once, then each entity's distinct context. Use the supplied schema, methodology, ruleset and category/location text where present; do not infer a missing contract from an old checkout or earlier task.
Retain the supplied task, actor, assessment, work-item and context hashes. A missing, stale or blocked_missing_full_context package needs corrected context from the invoking workflow. Do not manufacture hashes, missing preflight results or evidence of review.
Author the requested artifact
Use the work item's template and output path. Read semantic work for the relevant decision type and evidence rules.
- Identity: compare the actual candidates and entity context; preserve exact canonical IDs and versions for reuse. Do not replace identity work with field patches.
- Classification/location: choose a valid supplied code and retain the task-specific context binding and target path.
- Field repair: write only supported patch operations that resolve the listed action items, with source evidence and the required resolution metadata.
Preserve source-language information and add evidence-backed English for required multilingual fields. Do not invent scientific values or put mandatory fields into a trace to make a gate appear passed. If evidence cannot resolve an item, retain a specific blocker; use a deferral only when that item explicitly permits it.
Return to the workflow
Return the produced file paths, their work-item association and remaining blockers. The invoking workflow selects the current tiangong-foundry.semantic-input.v1 submission and lets Foundry validate hashes, context and applicability before deterministic apply.
Do not edit source/final row files, registered reports, profiles, grants, capsules, attempts or completion records. Do not issue database requests or commit/publish/delete commands. A semantic decision is not permission to write, and a local successful patch is not completed import or remote readback.