markitect-main/examples/infospace-with-history
tegwick e695ddfbbd infospace: process book-4-chapter-09
Extract entities, map to VSM, and synthesize analysis.
2026-02-19 22:32:07 +01:00
..
artifacts fix(example): standardise domain enum and source chapter format in schema/rules 2026-02-19 13:02:05 +01:00
output infospace: process book-4-chapter-09 2026-02-19 22:32:07 +01:00
schemas fix(example): standardise domain enum and source chapter format in schema/rules 2026-02-19 13:02:05 +01:00
templates fix(pipeline): retry on 0-entity response, save raw debug, improve template 2026-02-19 14:26:28 +01:00
infospace.yaml config(example): increase extract-entities max_tokens to 8000 2026-02-19 18:48:33 +01:00
INFRA-TASKS.md docs: metrics methodology, collection-level tasks, and infospace tooling roadmap 2026-02-18 23:53:21 +01:00
METRICS-METHODOLOGY.md docs: metrics methodology, collection-level tasks, and infospace tooling roadmap 2026-02-18 23:53:21 +01:00
process_chapters.py feat(example): migrate to infospace config with tooling integration (S3.1) 2026-02-19 02:29:53 +01:00
README.md feat(llm): add Gemini adapter and process book-1-chapter-05 2026-02-11 22:54:37 +01:00
TUTORIAL.md docs(infospace): document infospace.db and add to .gitignore 2026-02-18 22:27:08 +01:00

This example provides a tutorial and reference experiment for how to set up a viable infospace with history using markitect.

The task is to capture the knowledge from Adam Smith's The Wealth of Nations available digitally in the public domain as a transcript of the original text and transform and extend it to a collection of concepts and entities from a systems theoretical point of view based on Stafford Beer's Viable System Model that is consistent and complete.

The tutorial should explain how to use the concept of schemas to provide a scaffolding for how to structure the necessary information entities and define a set of prompts and instructions using the prompt dependency resolution infrastructure to incrementally inject chapters of the book.

The information space should utilize the option of keeping changes as git history. And define metrics for completeness and consistency.

While running the experiment no changes must be made to the markitect infrastructure.

If demand for optimization or fixing errors occurs, a list of corresponding tasks should be generated. It will be used to optimize the markitect infrastructure to then rerun the experiment to optimize tooling and infospace over time and again.

--worsch, 10th Feb. 2026