Skip to content
Aggregate Bundles
AutoXXS (320px)XS (375px)SM (640px)MD (768px)LG (1024px)XL (1280px)XXL (1536px)
SketchMaterialiOSTamagui
DataInjectionKeyPatternsServiceTransactionProcessResearchProductQualityPerformanceSpecDomainFunctionTechnologyArchitectureConfigMiddlewareDataDatabaseDrizzleMigrationModelop-sqliteSchemaSQLState ManagementDraftKeystoneMergePatchPatchesPersistenceReactiveRedoStoreUndoTestingDeviceFactoryIsolationTypeScriptZodTopicsCommunicationBidsNVCDesignDesign ImplicationsEducationPedagogyFoundationsPsychologyAttachmentFloodingRelatingAuthentic RelatingUIEditorReact Native

Aggregate Bundles

Fragment reference Aggregate Bundles
tags
agent

Aggregate bundles provide a “bird’s eye view” of the system. Instead of querying individual documents, agents can fetch these aggregates to perform cross-document analysis or coherence checks.

All aggregate bundles are located at dist/bundles/aggregate/{id}.toon and can be retrieved via get_document("aggregate/{id}").

Bundle IDContentsUse Case
actionsAll domain actions across all documentsVerify action naming and parameter consistency
api-referenceUnified API reference (actions, events, operations, errors)Comprehensive API coherence review
article-tagsTag cloud from all articlesContent categorization and discovery
atomsReusable content atomsAtom reuse and deduplication
bibliographyCollected citations and referencesBibliography completeness and formatting
changelogAll changesets sorted by date with affected filesUnderstand system evolution and recent hand-offs
componentsAll architectural components and their dependency graphAnalyze system topology and layer integrity
diagramsAll Mermaid diagrams across documentsDiagram inventory and consistency
errorsConsolidated registry of all declared domain errorsAnalyze error codes and coverage
eventsAll domain events across documentsEvent naming and payload consistency
examplesAll illustrative examples with tagsExample coverage and discovery
glossaryEvery term and definition from all domain glossariesPrevent duplicate or conflicting definitions
operationsAll request/response operations with input/outputAnalyze service contracts and state changes
policiesEvery business rule and policy grouped by domainCheck for cross-domain constraint conflicts
quotesCollected article quotesQuote attribution and discovery
roadmapMilestone-based roadmap with included features/flowsRelease planning and progress tracking
requirementsAll product and non-functional requirements with priorityTraceability audits and status reporting
settingsAll application configuration settingsSetting inventory and default value review
showroomSurface / wireframe galleryVisual design overview
surfacesAll surfaces with wireframe markupSurface inventory and cross-referencing
tagsTag documentation index (all *.tag.mdoc entries)Tag schema discovery and validation
toursAll guided product toursTour coverage and stop sequencing
traceabilityRequirement → feature mappingRequirement coverage analysis

Bundle Structure

Every aggregate bundle follows this common envelope:

{
"type": "aggregate",
"id": "api-reference|glossary|...",
"generatedAt": "ISO-8601-timestamp",
"sourceCount": number,
"items": []
}

The items array contains the specific data for that aggregate type.