knowledge-construction

Bilingual knowledge objects are generated by extracting structured data from staged DocMason sources to produce a knowledge.json file and a summary.md file that preserve source provenance and reference original artifacts.

Provenance preservation works by generating knowledge.json files and summary.md sidecars that explicitly reference source artifacts and derived affordances, ensuring every published knowledge object remains traceable to its original staged evidence.

Automating bilingual summary generation is best achieved by targeting the governed packet and pending-work scope defined by knowledge-base-sync, reading pending_work.json manifests, and outputting structured summary.md files for each assigned source.

Yes, building knowledge objects from DocMason evidence requires local file access and shell execution to read structured manifests like pending_work.json, artifact_index.json, and derived affordances to ensure accurate and traceable results.

No, the workflow specifically targets the governed packet and pending-work scope defined by knowledge-base-sync, meaning it processes only assigned sources within that bounded scope to ensure consistent and auditable results.

Required structured manifests include knowledge_base/staging/pending_work.json, knowledge_base/staging/sources/*/knowledge.json, artifact_index.json, and derived affordances, which are all read to ensure accurate and traceable knowledge extraction.