Manifest Structure Reference
Complete section specifications for the extension handoff manifest.
Header (always included)
Extension Manifest — {Extension Name}
Generated by: ALDC Conductor (v{version})
Date: {YYYY-MM-DD}
Pipeline complexity: {LOW | MEDIUM | HIGH}
Target consumers: {CIRCE | DELFOS | CIRCE + DELFOS}
Repository:
Repo: {repo URL}
Branch: {branch}
AL source path: {src/ | app/}
Spec reference: {path to al-spec.md in repo}
Section: CIRCE — MCP Connection Context (CIRCE only)
Include ONLY when target includes CIRCE. This section is intentionally lightweight. The BC MCP server (configured on Page 8351 "Model Context Protocol (MCP) Server Configurations") already exposes all API pages as tools automatically. The manifest only provides connection coordinates and a map of relevant tool names.
Connection coordinates: BC Environment, Company, MCP Configuration Code.
Relevant MCP Tools table: entityName, Domain, Purpose. In static mode, tools follow the naming pattern List<object>_PAG<ID> (read), Create<object>_PAG<ID> (create), ListUpdate<object>_PAG<ID> (modify), Delete<object>_PAG<ID> (delete), <action>_PAG<ID> (bound actions). In dynamic mode (required when >70 API pages), only 3 meta-tools appear: bc_actions_search, bc_actions_describe, bc_actions_invoke.
Tool lists: Custom tools created by this extension, Standard BC tools relevant to this domain.
Repo reference: URL for when the CIRCE agent needs to inspect business logic via GitHub MCP.
Do NOT include field-level details, OData routes, action parameters, or authentication details in this section. The MCP server provides all of that automatically when Copilot Studio connects with the environment + company + configurationName coordinates.
Section: Published API Pages (DELFOS only)
Include ONLY when target includes DELFOS. For each API page in the extension:
| Field | Description |
|---|---|
| OData v4 route | Full route including publisher, group, version |
| Source table | The BC table exposed by this page |
| Key fields | ODataKeyFields (typically SystemId) |
| Field table | AL Field Name, API Field Name, Type, Description |
| Filters supported | Notable filter capabilities |
| Repo source path | Relative path to the .al file |
Section: Published API Queries (DELFOS only)
Include ONLY when target includes DELFOS. For each API query in the extension:
| Field | Description |
|---|---|
| OData v4 route | Full route including publisher, group, version |
| Purpose | What this query aggregates or exposes |
| Source tables | Tables involved in the query |
| Columns table | Column Name, Type, Source |
| Repo source path | Relative path to the .al file |
Section: Data Structure (DELFOS only)
Include ONLY when target includes DELFOS. For each table created or extended by the extension:
| Field | Description |
|---|---|
| Purpose | What the table stores |
| Primary key | Key field(s) |
| Records volume estimate | Low (<1K), Medium (1K–100K), High (>100K) |
| Fields table | Field Name, Type, Dimension/Measure Candidate, Description |
| Relations table | Field, Related Table, Related Field, Cardinality |
| Table extension base | Base table name (if tableextension) |
| Repo source path | Relative path to the .al file |
Dimension/Measure classification: Text, Code, Date, Boolean → Dimension. Decimal, Integer (quantities/amounts) → Measure. When ambiguous, mark as (review) so the DELFOS Architect validates.
Section: Star Schema Hints (DELFOS only)
Include ONLY when target includes DELFOS. These are suggestions for the DELFOS Architect, not prescriptions.
Suggested fact tables: Tables that contain transactional data with numeric measures.
Suggested dimension tables: Tables that provide descriptive context (lookups, categories, entities).
Suggested relationships table: Fact Table, Fact Key, Dimension Table, Dimension Key, Cardinality.
Known gaps: Data that would enhance the model but is not currently stored or exposed. Include DAX measure suggestions where applicable.
bc-data-source-mapping compatibility: YES or NO. When YES, DELFOS can feed the manifest data directly into the bc-data-source-mapping skill without additional lookups.
Mark any uncertain mapping with (review).
Footer (always included)
Consuming instructions:
CIRCE: Copy this manifest to your CIRCE workspace. The CIRCE Architect
will use the MCP Connection Context section to configure the Dynamics 365
Business Central connector in Copilot Studio. Use GitHub MCP for deeper
inspection of business logic in codeunits and event subscribers.
DELFOS: Copy this manifest to your DELFOS workspace and reference it when
invoking the Data Modeling Expert. The Published API Pages and Data Structure
sections feed directly into the bc-data-source-mapping skill. Star Schema
Hints provide a starting point for the DELFOS Architect's validation.
Skills Evidencing block: skill loaded, source data inspected, sections generated, HITL gates passed.