Our books and scientific papers emerge from a structured, versioned and human-controlled production process โ supported by GAWP.
We do not use AI to generate publications at the push of a button. We build a traceable production process in which people, knowledge, specialised agents, reviews, versioning and quality gates work together.
Selected current book versions from our production archive. We do not invent titles here.
A selection of papers and conference contributions available in the project. This list is an entry point, not a claim of completeness for every historical revision.
Note: Additional files exist under public/books and public/papers; this page shows a curated selection of current versions.
For us a publication is not an isolated file but the outcome of a connected workflow:
Idea โ Knowledge โ Sources โ Structure โ Manuscript โ Review โ Revision โ Production โ Release
Every project starts from a subject matter: papers with research question, contribution and related work; books with audience, value proposition and depth. These requirements are increasingly documented explicitly.
We keep source, derived information, interpretation and own conclusions distinct. GAWP helps connect sources and text in a traceable way โ without replacing source criticism or authorship.
Before drafting, we define an architecture. Papers typically cover problem, related work, method, contribution, evaluation and conclusion; books may include parts, chapters, figures, glossary, bibliography and indexes. Structures evolve under version control.
A publication is not created by one universal prompt. GAWP separates specialised steps such as research support, structure, language, terminology, citation and layout checks into traceable tasks.
GAWP does not replace authorship or scientific responsibility. Authors decide on thesis, sources, interpretation, accepted changes and release. Agents analyse and propose; responsibility stays with people.
Audit analyses without changing content. Propose formulates concrete changes. Apply implements only approved changes. Separating analysis from modification is a core quality principle.
Manuscripts pass multiple cycles (subject-matter, language, source/consistency, production). Specialist books may add expert, lay, audience and figure reviews.
Outcomes are checked against requirements and scored PASS, PASS_WITH_WARNINGS or FAIL, making unfinished stages visible.
Publications evolve as versioned products (e.g. v1.00 โ v1.01). Reviews and releases can be tied to specific states; digital works can continue after first release.
Typical chain: concept โ sources โ architecture โ chapters โ reviews โ figures โ literature/glossary/index โ layout โ website/print โ quality gate โ release. Not every project uses every format.
Papers need a clear research question, defined contribution, related work, sound argumentation, correct sources and venue formalities. GAWP helps treat these as contracts and gates.
One knowledge base can feed a paper, chapter, book, website text or documentation โ adapted to language, scope and audience. Successful workflows should be reusable while projects remain separate.
We do not claim error-free books, fully automatic science or author replacement. Our claim: structured, reproducible, versioned, agent-supported and human-controlled.