knowledge

Knowledge and Documentation Systems

How AISYSTEMS separates public documentation, internal knowledge, retrieval evidence and authority.

service technical-lead evaluate

AI systems need clear source boundaries. Public docs, internal knowledge, private workspace files and policy authority should not be mixed into one uncontrolled context.

Source classes

  • Public documentation for visitors and crawlers
  • Approved public context for public agents
  • Internal knowledge for private operators
  • Policy and contracts for system enforcement
  • Audit logs for evidence, not public answers

LLM-ready docs

Good public docs have stable URLs, short pages, summaries, metadata, sitemap, llms.txt, llms-full.txt and a structured catalog.

AISYSTEMS pattern

The public docs site uses Markdown source, generated HTML, docs.json, llms.txt and llms-full.txt so humans and AI tools can find the right page without crawling everything.