Increment I5: Knowledge and connections¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
A design artefact, not a tracker
This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).
Outcome. A run on an existing repository uses scoped retrieval with citations, and external systems connect through governed connectors.
Depends on: I4 · Elaboration: epics and features (rolling wave) · Azure DevOps CSV of this increment
Demonstrations¶
- An ingested repository is searchable only inside its tenant and project scope.
- An agent answer cites the retrieved sources.
- A webhook from an external system is verified, deduplicated and delivered.
Services delivered in this increment¶
| Service | Role | Depth | Scope in this increment | Repository |
|---|---|---|---|---|
ContextBuilderService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.ContextBuilderService |
KnowledgeIngestionService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService |
MemoryPromotionService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.MemoryPromotionService |
RepositoryIntelligenceService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService |
VectorMemoryService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.VectorMemoryService |
McpServerRegistryService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
ConnectorRegistryService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService |
IntegrationService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.IntegrationService |
WebhookGatewayService |
edge-service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.WebhookGatewayService |
Stub register¶
No stub is declared in this increment.
Before development¶
No template or library work is placed in this increment.
Features by epic¶
Knowledge Platform (PF-04)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-023 ContextBuilderService: complete deliveryContextBuilderService is the service of bounded context BC-09 (Context Assembly). The context engineering plane — plans what a task needs (mandatory instructions, task, conversation state, repository state, knowledge, graph neighbours, episodic memory, diff, tool results), retrieves and expands candidates, ranks, deduplicates, compresses and budgets tokens, and records an immutable context snapshot that says what was used and why (BC-09). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.ContextBuilderService. |
development | outline | backend-developer | — | — |
AIFACTORY-FEAT-024 KnowledgeIngestionService: complete deliveryKnowledgeIngestionService is the service of bounded context BC-10 (Sources & Ingestion). Owns knowledge sources and collections, immutable source snapshots, the ingestion pipeline (parse, normalize, metadata, chunk, publish to indexes with ACL propagation), incremental sync, staleness and deletion lineage; code, documentation, library and template sources are source types, not services (BC-10). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService. |
development | outline | backend-developer | — | — |
AIFACTORY-FEAT-025 MemoryPromotionService: complete deliveryMemoryPromotionService is the service of bounded context BC-13 (Promoted Memory). The governed memory lifecycle — observations from completed runs become candidate memories, are classified (temporary, episodic, semantic candidate, procedural candidate, discard), checked against evidence, scored for confidence, reviewed per policy and promoted into scoped, provenance-carrying, expiring memory; agent opinions never become organizational facts without review (BC-13, D32). Its own repository is ConnectSoft.AI.SoftwareFactory.MemoryPromotionService. |
development | outline | backend-developer | — | — |
AIFACTORY-FEAT-026 RepositoryIntelligenceService: complete deliveryRepositoryIntelligenceService is the service of bounded context BC-39 (Repository Intelligence). Repository indexes per revision — file tree, symbols, types, dependencies, calls, references, Git history, ownership, build and test relationships — built from repository snapshots and exposed as read tools so that large repositories are never dumped into model context (BC-39, original design §33). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService. |
development | outline | backend-developer | — | — |
AIFACTORY-FEAT-027 VectorMemoryService: complete deliveryVectorMemoryService is the service of bounded context BC-11 (Retrieval & Indexes). The retrieval module (historical name kept from the June-2026 catalog) — vector, full-text, symbol, metadata, graph-projection and temporal retrieval combined under trusted scope with ACL enforced before top-k, citations with source version and index revision, embedding and index revisions pinned to profiles, and rebuildable derived indexes (BC-11, ADR-0013). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.VectorMemoryService. |
development | outline | backend-developer | — | — |
Tools & MCP Platform (PF-05)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-031 McpServerRegistryService: complete deliveryMcpServerRegistryService is the service of bounded context BC-08 (Tool Execution). Registry of MCP servers the Factory consumes or exposes — transport, endpoint or connection, authentication (on by default), governance policy, discovered tools, resources and prompts bound to tool descriptors and knowledge sources, handshake health and the ModelOps-like lifecycle from registration to retirement (BC-08, ADR-0022). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.McpServerRegistryService. |
development | outline | backend-developer | — | — |
Integration Platform (PF-06)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-035 ConnectorRegistryService: complete deliveryConnectorRegistryService is the service of bounded context BC-17 (Connectors & Webhooks). Connector descriptors (capability interfaces, retry and rate-limit profiles, webhook schemes, configuration forms) with provider certification, subscriptions to inbound events, verified inbound deliveries and outbound deliveries with receipts; first-party clients (Azure DevOps, GitHub, Deputy, Braze, Bill, Twilio, Israel019, ACS, GA, Meta) are adapters behind descriptors (BC-17). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService. |
development | outline | backend-developer | — | — |
AIFACTORY-FEAT-036 IntegrationService: complete deliveryIntegrationService is the service of bounded context BC-16 (Connections). Tenant-scoped connections to external systems — provider, endpoint policy, credential references (never values), grants that say which projects, agents and tools may use a connection, rotation metadata and health — with every use brokered as a short-lived credential by the Secret Broker (BC-16). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.IntegrationService. |
development | outline | backend-developer | — | — |
AIFACTORY-FEAT-037 WebhookGatewayService: complete deliveryWebhookGatewayService is the edge service of bounded context BC-17 (Connectors & Webhooks). The conditional inbound ingress for vendor webhooks — signature verification per connector scheme, replay-window and deduplication checks, rate limiting and payload capture — that emits verified deliveries to the connector module and never dispatches anything itself (BC-17, GW-06). Its own repository is ConnectSoft.AI.SoftwareFactory.WebhookGatewayService. |
development | outline | backend-developer | — | — |
Ecosystem component extensions¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-103 Config Platform integration when it existsFeature flags and runtime configuration of the Factory move to the Config Platform once that product is implemented; until then the services read configuration from their own options and degrade without it, as the model's dependency rows say. Component: Feature management and configuration (Config Platform) (develop). |
development | outline | backend-developer | — | — |
Factory assets: workflow definitions, agents and skills¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-122 Workflow definition: Capability gap analysisThe workflow definition capability-gap-analysis as a published asset: Finds the APIs, data and templates a Service Blueprint needs but the estate lacks, by querying the template catalog, the knowledge platform and repository intelligence, and classifies each gap as build, reuse or defer. It has 4 steps, names the agents enterprise-architect and the tools knowledge-search, and is executed by WorkflowEngineService under Run Control. |
development | outline | solution-architect | — | — |
AIFACTORY-FEAT-123 Workflow definition: Documentation syncThe workflow definition documentation-sync as a published asset: Regenerates a product's documentation site from the model after a merged change, writes the narrative deltas, validates the build and proposes the documentation change set. It has 5 steps, names the agents documentation-site-generator, documentation-writer and the tools build-and-test, propose-change-set, and is executed by WorkflowEngineService under Run Control. |
development | outline | solution-architect | — | — |
AIFACTORY-FEAT-124 Workflow definition: Guides generationThe workflow definition guides-generation as a published asset: Drafts guides and tutorials for a generated product as artifacts for human review; nothing is published by the run. It has 4 steps, names the agents documentation-writer and the tools none, and is executed by WorkflowEngineService under Run Control. |
development | outline | solution-architect | — | — |
AIFACTORY-FEAT-149 Workflow definition: Documentation blueprintThe workflow definition documentation-blueprint as a published asset: Builds the Documentation Blueprint from the Service and Module Blueprints: the documentation site structure, the page families per module, the audiences and the sources each page is generated from; validated against the DSL. It has 5 steps, names the agents documentation-writer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control. |
development | outline | solution-architect | — | — |
Outcome verification¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-143 Demonstrate I5: Knowledge and connectionsThe outcome of increment I5 is demonstrated end to end and the evidence is recorded: A run on an existing repository uses scoped retrieval with citations, and external systems connect through governed connectors. Demonstrations: An ingested repository is searchable only inside its tenant and project scope. An agent answer cites the retrieved sources. A webhook from an external system is verified, deduplicated and delivered. |
development | outline | qa-engineer | — | — |
Requirements this increment touches¶
FR-01, FR-02, FR-05, FR-07, FR-08, FR-11, FUX-01, FUX-02, FUX-06, FUX-09, FUX-10, FUX-11, FUX-12, NFR-02, NFR-03, NFR-05, NFR-07, NFR-09, NFR-11, NFR-13, NFR-16, NFR-18, XL-02, XL-03, XL-07, XL-08, XL-10, XL-13, XL-14, XL-15, XL-16