AIFACTORY-FEAT-094: Import of the backlog draft by the owner¶
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).
Epic Engineering readiness · Increment I0 Readiness · State elaborated · Route human-approval · Build order 49 of 185 (Factory code)
Every owner decision the first wave depended on is recorded: the derived decisions D70, D71 and D74 and the stub register of the first outcome (D80), the Scrum process (D81), the waiver that lets Draft releases run before the evaluation gate exists (D83) and the import without an area path (D85). One act stays with the owner: importing the draft into Azure DevOps, because no session of the Factory design work has a connection to it.
| Delivers | — |
| Stubs | — |
| Realizes | adrs: ADR-0027, ADR-0028, ADR-0021 |
| Requirements | — |
| Depends on | — |
| Sources | docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md |
AIFACTORY-US-378: Owner decisions: the import files carry the Scrum types and no area path, each packed or per-epic file holds at most 1,000 rows, and a guide tells the owner what to import in which order¶
enabling · persona platform-admin
As a platform admin, I want import files and a guide that match what the owner decided about the tracker, so that the owner can import the draft in one sitting and nothing is created before that.
ADR-0029 decision 1 keeps the backlog a model kind of this repository: nothing here creates a work item in a tracker, and importing the draft is a separate, explicit act of the owner. Two decisions of the owner shape the import files. The Azure DevOps project uses the Scrum process (decision D81), so the export names the work item types Epic, Feature, Product Backlog Item and Task. The import carries no area path (decision D85), so the items land in the root area of the project and are moved later if needed. Both are recorded in model/backlog/backlog.yaml, which also states that nothing was created in a tracker. The files are generated from the model under docs/backlog/export, with the hierarchical title columns, the description, the acceptance criteria, the tags and the stack rank of the derived build order. They are of four sorts. The whole draft, aifactory-backlog-ado.csv, is the complete reference file: it holds more than 1,000 rows and is not an import file. The packed files aifactory-backlog-ado-NN.csv hold whole epics in build order, at most 1,000 rows each with parents first, and are the way to import the whole draft. The per-epic files hold at most 1,000 rows each as well. A per-increment file is generated without that limit and serves an import only while it stays within 1,000 rows. This PBI delivers the page that tells the owner how to use them. The guide states which file set serves which intent, the whole draft through the packed files in their order or one increment alone through its file while that file stays within 1,000 rows, the mapping of the four types, that a parent row precedes its children inside a file and across the packed files, and what to compare after the import: the count of items per type against the counts the generator reports, and the bracketed identifier at the start of every title. It also states what the files leave out by design: no date, estimate, assignee, sprint or capacity, because progress and people live in the tracker and never here (ADR-0029 decision 6). The guide decides nothing that is still open: the project to import into and the file set to use stay with the owner and are recorded as open by AIFACTORY-US-379. The files are never edited by hand; a change of the model regenerates them, and the check of the site fails when one is stale.
Acceptance criteria
| AC1 | Given model/backlog/backlog.yaml with the Scrum process and no area path, when the import files are generated, then every file under docs/backlog/export names the work item types Epic, Feature, Product Backlog Item and Task and holds no area path column, each packed file aifactory-backlog-ado-NN.csv and each per-epic file holds at most 1,000 rows with a parent row before its children, inside each file and across the packed files, and the whole draft aifactory-backlog-ado.csv is the complete reference file and is not an import file (ADR-0029 decision 8). |
| AC2 | Given the import guide page, when the owner reads it, then it names the packed files in their order as the way to import the whole draft, a per-increment file as the way to import one increment only while that file stays within 1,000 rows, and the whole draft docs/backlog/export/aifactory-backlog-ado.csv as the reference file that is not imported; it names the mapping of the four types and the comparison to make after the import, the count of items per type and the bracketed identifier in every title, and it states that nothing in this repository creates a work item (ADR-0029 decision 1). |
| AC3 | Given the generated files and the guide, when they are searched, then no row and no line carries a date, an estimate, an assignee, a sprint or a capacity, and python -I tools/docs_model check fails when a file under docs/backlog/export differs from what the model generates (ADR-0029 decision 6). |
| Traces: adrs | ADR-0029 |
| Sources | docs/architecture/adr/0029-build-backlog-as-a-model-kind.md, docs/backlog/index.md, docs/backlog/export/aifactory-backlog-ado.csv, model/backlog/backlog.yaml, handoffs/2026-10-09-independent-review/open-items.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1550 Import guide page for the backlog draft |
documentation | A page of this site, linked from the index of the handoff records and from the navigation of the site and from no generated page, that names the generated files under docs/backlog/export and the intent each serves: the packed files in their order for the whole draft, a per-increment file only while it stays within 1,000 rows, the per-epic files, and the whole draft as the reference file that is not imported; it names the mapping of the types Epic, Feature, Product Backlog Item and Task, the comparison of counts and identifiers after the import and the fields the files leave out by design; it names no project, no person and no date. | ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-TASK-1551 Verify the import files against the tracker settings of the model |
verification | Run python -I tools/docs_model check; the files under docs/backlog/export are fresh, each packed file aifactory-backlog-ado-NN.csv and each per-epic file holds at most 1,000 rows with parents first, the four type names equal those of model/backlog/backlog.yaml and no file has an area path column; a read of the guide finds the whole draft named as the reference file and not as an import file, which proves AC1 to AC3 of AIFACTORY-US-378 (ADR-0029). |
ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-US-379: Owner decisions: every decision that still belongs to the owner is recorded as open with what it blocks, and no backlog item decides it¶
enabling · persona platform-admin
As a platform admin, I want one register of the decisions that are still open and whose they are, so that no writer, agent or backlog item quietly decides what the owner has not decided.
Some decisions the build depends on are not taken, and the worst outcome is a value that someone invented and that reads as decided. This PBI keeps one register of them in the open items of the handoff records, each row marked open, and sets the rule that goes with it. The register is complete by a rule and not by a selection. It holds every row of handoffs/2026-10-09-independent-review/open-items.md whose closing column names the owner and that is not marked closed, every item that the decisions D113 to D115 record as left open, every open question recorded under handoffs/2026-10-09-independent-review/pbi-reviews, and every input of the owner that a PBI under model/backlog/pbis states (D140). An input of the owner is a value the model leaves to the owner and a PBI says is never invented; its row names the PBI that states it, says that the owner supplies the value and never states the value. The inputs an I1 service refuses to start without, or without which it discovers nothing, are also entries of the I1 precondition register of AIFACTORY-US-1339, which the owner supplies before the I1 run and which are checked before it: Usage:Budgets:DefaultLimitUsd, Usage:Budgets:DefaultPeriod and Usage:Budgets:PlatformLimitUsd, the section Usage:Estimates and the pricing revisions of the meters of CostUsageService, the Sandbox pool values of ExecutionCapacityService (boundary, egress, region, size and workspace medium), the template-feed project of the platform tenant of TemplateRegistryService and the source of the tenant region of ProjectService. Three rows are the ones the owner named as still theirs. The tracker import settings: the process and the area path are decided (decisions D81 and D85), while the project to import into, the choice between the packed files and one increment file, and a later move of items out of the root area are not. The team: its shape, its capacity and the owners of the work stay deferred by direction of the owner, and the tracker carries people and dates, never this repository (ADR-0029 decision 6). The units of the seven usage dimensions: the unit and the conversion factor of each of the seven meters that docs/reference/schemas/usage-record.schema.json lists, model.tokens, runs.accepted, runs.completed, tools.invocations, sandbox.minutes, storage.gb and product.capacity, are an input of the owner; the metering PBIs fix the rule and the shape of the map and name no value. From the open items the register further holds: the adoption of the canonical AI and messaging decision by its owner; the questions Q-04 and Q-08 to Q-16 of the decision log; the five differences between ADR-0024 and its primary documentation; the consumers of a deletion order outside eight platforms; the three points on which hand pages and the model differ; the repository name of the Studio front end; the template parameter bindings, which the owner and the template owners confirm or correct; and the approval of each epic of the PBI campaign. From decision D115 it holds: the treatment of a project, release or environment that was never announced to the gate states of Run Control; the call that sets the validation reference of an artifact; a read operation for the reconciliation result of usage; the consumer of the three aggregator events of the fleet profile and the health address and criticality of an observed workload; whether a skill package may name a tool of another package; and the names a writer chose that the owner may rename. From the review records of the campaign it holds the open questions of each run, those of this epic among them: the name of the evidence event type and one or two descriptors for the audit evidence record. Where the commands of the command-line client belong is no longer open: they are the I1 feature command-line-client-commands, which the done_when of the epic engineering-readiness names beside typed-gateway-clients (D140). Two approvals of this epic recur, and each has a row that stays open: the creation of each repository, and the list of the database names of the local and acceptance environments. Each row states the question, what is already decided, what it blocks and that the owner decides. The rule: an item that depends on an open row names the row and states no value for it. When the owner decides, the row is closed with the decision identifier, the decision log gains its row and the model file or ADR that carries the decision changes in the same change.
Acceptance criteria
| AC1 | Given the register of open decisions, when it is read, then it holds one row each for the tracker import settings, the team and the units of the seven usage dimensions, each marked open, with what is already decided (the Scrum process and no area path in model/backlog/backlog.yaml; the seven meters in docs/reference/schemas/usage-record.schema.json), what the row blocks and that the owner decides it (ADR-0029 decisions 1 and 6). |
| AC2 | Given the backlog and the model, when they are searched for a value of an open row, then no file under model/backlog names a team member, a capacity, a date or a sprint, no file states a unit or a conversion factor for a usage dimension as decided, and an item that depends on an open row names that row (ADR-0029 decision 6; model/backlog/backlog.yaml). |
| AC3 | Given the four sources of the register, when it is compared with them, then every row of handoffs/2026-10-09-independent-review/open-items.md whose closing column names the owner and that is not marked closed, every item that the decisions D113 to D115 record as left open in handoffs/2026-10-09-independent-review/decision-log.md, every open question recorded under handoffs/2026-10-09-independent-review/pbi-reviews, and every input of the owner that a PBI under model/backlog/pbis states, the I1 inputs that D140 enters in the precondition register of AIFACTORY-US-1339 among them (Usage:Budgets:DefaultLimitUsd, Usage:Budgets:DefaultPeriod, Usage:Budgets:PlatformLimitUsd, Usage:Estimates, the pricing revisions, the Sandbox pool values, the template-feed project of the platform tenant and the source of the tenant region), has its row with the question, what is decided, what it blocks, the PBI that states it where it is an input, and the owner as the one who decides or supplies it, and none is marked closed without a decision identifier and none states the value (ADR-0029 decision 1; docs/architecture/adr/0024-durable-execution-substrate.md records the five differences as revisit triggers for the owner). |
| AC4 | Given the owner decides an open row, when the decision is recorded, then the row is closed with the decision identifier, and the model file or ADR that carries the decision changes in the same change; until then the row stays open and nothing under docs/backlog or model/backlog reads as decided (ADR-0029 decision 1). |
| Traces: adrs | ADR-0029 |
| Sources | handoffs/2026-10-09-independent-review/open-items.md, handoffs/2026-10-09-independent-review/decision-log.md, docs/architecture/adr/0029-build-backlog-as-a-model-kind.md, docs/architecture/adr/0024-durable-execution-substrate.md, docs/reference/schemas/usage-record.schema.json, model/backlog/backlog.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1552 Register of the decisions that are still open for the owner |
documentation | The open items of the handoff records hold one row per open decision, complete by the rule of the four sources: every row of open-items.md whose closing column names the owner and that is not marked closed (the import of the backlog draft with its tracker settings, the team, the adoption of the canonical AI and messaging decision, the questions Q-04 and Q-08 to Q-16, the five differences of ADR-0024, the consumers of a deletion order outside eight platforms, the three points on which hand pages and the model differ, the repository name of the Studio front end, the template parameter bindings and the approval of each epic of the PBI campaign), every item decision D115 leaves open (the never announced gate state, the validation reference of an artifact, the unit and conversion factor of each of the seven meters of docs/reference/schemas/usage-record.schema.json, the read operation for the reconciliation result, the consumer of the aggregator events, the health address and criticality of an observed workload, the tool of another skill package and the names a writer chose), every open question under pbi-reviews (for this epic the name of the evidence event type and one or two descriptors for the audit evidence record), every input of the owner that a PBI states, with the PBI that states it (D140; the I1 inputs of the precondition register of AIFACTORY-US-1339 among them: the budget defaults and the platform limit, Usage:Estimates, the pricing revisions, the Sandbox pool values, the template-feed project of the platform tenant and the source of the tenant region) and the two recurring approvals of this epic (the creation of each repository, the list of database names); each row states the question, what is already decided, what it blocks and that the owner decides, and is marked open; no row states a value. |
ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-TASK-1553 Verify that no backlog item decides an open row |
verification | Run python -I tools/docs_model validate; the rule against dates, estimates and assignees passes over model/backlog, a search of model/backlog and docs/backlog for a unit or a conversion factor of a usage dimension, a team member and a capacity finds none stated as decided, and a comparison of the register with open-items.md, with the rows D113 to D115 of the decision log and with the files under handoffs/2026-10-09-independent-review/pbi-reviews finds no open item without a row, and a search of model/backlog/pbis for the words input of the owner and owner input finds every stated input with its row and the I1 inputs of D140 also in the precondition register of AIFACTORY-US-1339, which proves AC1 to AC4 of AIFACTORY-US-379 (ADR-0029). |
ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-US-380: Owner decisions: every accepted decision of the first wave has its row in the decision log and its effect in the model or in an ADR, and the validator passes¶
evidence · persona platform-admin
As a platform admin, I want proof that each decision the owner took is carried by the model or by an ADR, so that a decision cannot be lost between the log that records it and the files the build reads.
This PBI is the proof of the feature: a recorded decision is checkable only when the file the build reads says the same as the log that records it. The decisions of the first wave are these. The derived decisions D70 and D71, the role contract corrections and the readiness members added for required role inputs, were accepted by the owner and are decisions 5 and 6 of ADR-0027. Decision D74, a relational store per service, is decision 5 of ADR-0028 and the rows of model/stores.yaml. Decision D80 accepted them together with the stub register of the first outcome, with AuditService and CostUsageService delivered complete in increment I1, which the features of the backlog state. Decision D81, the Scrum process, and decision D85, the import without an area path, are the tracker settings of model/backlog/backlog.yaml. Decision D83, the waiver that lets a Draft release run before the evaluation gate exists, only in the acceptance environment and in projects a platform-scope policy rule names as internal, is the amendment of ADR-0021. The decisions of the backlog campaign follow the same path: D111, the PBI format, is the amendment of ADR-0029; D112, the freeze of that format after the pilot, is carried by the ratchet file model/backlog/progress.yaml, which names the pilot features; D113, D114 and D115 each hold many decided points, and the last column of the decision log names their carriers, most of them model files, so the trace has one row per decided point of these three and not one row per decision. The ADR amendments are among the carriers: those of ADR-0015 on a resource of another tenant, on the role order, the one audience of a user token and the workload token, and on role writes, that of ADR-0014 on envelopes per event family and the failure class, and that of ADR-0028 on the Factory profile switch and the feed. The other points are carried by model and schema files: the Held state and ChangesRequested by model/services/control-plane/RunControlService.yaml, the optional environmentId by docs/reference/schemas/run-submission.schema.json, onExpiry and the limit of re-requests by the approval rule of ApprovalPolicyService, failure_policy and the retry of write steps by the workflow schema and the validator, SubmitEvidence by AuditService, the optional failure class by AgentRuntimeService, and the Metering service of increment I4 by the components and the backlog. The evidence is a trace on one page of this site: per decision the row of the decision log, the ADR section or the model field that carries it, and the check that reads it. A decision or a decided point whose carrier is missing or behind is listed as a gap, and the feature is not accepted while a gap is listed. One gap is known when this PBI is written: the state enumeration of docs/reference/schemas/approval.schema.json has no ChangesRequested and the request has no onExpiry and reRequestsLeft; AIFACTORY-TASK-1568 of feature contracts-package closes it. The trace adds no decision and changes no carrier.
Acceptance criteria
| AC1 | Given the decisions D70, D71, D74 and D80, when the trace is read, then each names its row in the decision log and its carrier: decisions 5 and 6 of ADR-0027, decision 5 of ADR-0028 with one store per service in model/stores.yaml, and the complete deliveries of AuditService and CostUsageService in increment I1 in model/backlog/features/governance.yaml and model/backlog/features/control-plane.yaml. |
| AC2 | Given the decisions D81, D83 and D85, when the trace is read, then the Scrum process with the types Epic, Feature, Product Backlog Item and Task and the absent area path are the tracker settings of model/backlog/backlog.yaml, and the waiver for Draft releases is the amendment of ADR-0021, which names the acceptance environment and the internal projects and never waives publication. |
| AC3 | Given the decisions D111 to D115, when the trace is read, then D111 names the amendment of ADR-0029 for the PBI format and D112 the pilot features of model/backlog/progress.yaml for its freeze, and the trace holds one row per decided point of D113, D114 and D115 with the carrier the last column of handoffs/2026-10-09-independent-review/decision-log.md names for it, a field of a model file, a schema file or an ADR amendment, and the check that reads it: the Held state and ChangesRequested in model/services/control-plane/RunControlService.yaml, the optional environmentId in docs/reference/schemas/run-submission.schema.json, onExpiry in model/services/governance/ApprovalPolicyService.yaml, failure_policy and the retry of write steps in model/schemas/workflow.schema.json and tools/docs_model/validate.py, SubmitEvidence in model/services/governance/AuditService.yaml and the amendments of ADR-0014, ADR-0015 and ADR-0028 among them; a point whose carrier is missing or behind, such as the state enumeration of docs/reference/schemas/approval.schema.json without ChangesRequested, is listed as a gap. |
| AC4 | Given the repository with the trace, when python -I tools/docs_model validate runs, then it reports no error, every ADR and every model or schema file the trace names exists, and the trace lists every decision or decided point without a carrier as a gap; the feature is accepted only when no gap is listed (ADR-0029 decision 1). |
| Traces: adrs | ADR-0014, ADR-0015, ADR-0021, ADR-0027, ADR-0028, ADR-0029 |
| Sources | handoffs/2026-10-09-independent-review/decision-log.md, docs/architecture/adr/0021-quality-gates.md, docs/architecture/adr/0027-generation-input-contract.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/adr/0029-build-backlog-as-a-model-kind.md, model/backlog/backlog.yaml, model/stores.yaml, model/services/control-plane/RunControlService.yaml, model/services/governance/ApprovalPolicyService.yaml, model/schemas/workflow.schema.json, docs/reference/schemas/approval.schema.json |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1554 Trace of the accepted decisions to the ADR sections and model fields that carry them |
documentation | A page of this site with one row per accepted decision of the first wave (D70, D71, D74, D80, D81, D83, D85, D111 and D112) and one row per decided point of D113, D114 and D115: the row of the decision log, the carrier that the last column of the decision log names for the point (a field of a file under model/, a schema file or an ADR amendment) and the check that reads it; a point whose carrier is missing or behind, such as the state enumeration of docs/reference/schemas/approval.schema.json without ChangesRequested, is listed as a gap; the page adds no decision and is linked from the index of the handoff records and from no generated page. |
ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-TASK-1555 Verify every carrier of the trace |
verification | Run python -I tools/docs_model validate; it reports no error, and a read of each row of the trace against docs/architecture/adr, the model and schema files it names and model/backlog/backlog.yaml finds the carrier it names or the gap it lists, which proves AC1 to AC4 of AIFACTORY-US-380 (ADR-0029). |
ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-US-135: Import of the backlog draft by the owner is delivered¶
enabling · persona platform-admin
As a platform admin, I want every owner decision of the first wave recorded and the backlog draft ready for the import by the owner, so that the build starts from decisions that are written down and from a tracker only the owner filled.
This is the integration PBI of the feature. Every owner decision the first wave depended on is recorded: the derived decisions D70, D71 and D74 and the stub register of the first outcome (D80), the Scrum process (D81), the waiver that lets Draft releases run before the evaluation gate exists (D83) and the import without an area path (D85), followed by the decisions of the backlog campaign (D111 to D115). AIFACTORY-US-380 proves that each of them is carried by an ADR or by the model. AIFACTORY-US-379 records what is still open as open: the tracker import settings beyond process and area path, the team, and the units of the seven usage dimensions, beside the further open rows of the handoff records. AIFACTORY-US-378 delivers the import files and the guide. One act stays with the owner: importing the draft into Azure DevOps, because no session of the Factory design work has a connection to it. The owner imports the packed files in their order, or one increment file while it stays within 1,000 rows, into the root area of a project that uses the Scrum process, as Epic, Feature, Product Backlog Item and Task, with no area path column. Nothing is imported before the owner does it, nothing in this repository creates a work item, and the backlog of the model stays marked as not created in a tracker until the owner records the import. The feature is done when the three outputs exist, are linked from the handoff records and pass the validator, and the import itself is recorded by the owner as done or stays open with the owner.
Acceptance criteria
| AC1 | Given the tasks of AIFACTORY-FEAT-094 are done, then the import guide, the register of open decisions and the trace of the accepted decisions exist in ConnectSoft.AI.SoftwareFactory.Documentation, are linked from the index of the handoff records, handoffs/2026-10-09-independent-review/INDEX.md, and from the navigation of the site, are linked from no generated page, and name the decisions that ADR-0027, ADR-0028 and ADR-0021 carry. |
| AC2 | Given the repository with those outputs, when python -I tools/docs_model validate runs, then it reports no error and no warning (ADR-0029 decision 6: no item carries a date, an estimate or an assignee). |
| AC3 | Given the backlog draft, when the owner imports it, then the items land in the root area of a project on the Scrum process as Epic, Feature, Product Backlog Item and Task; before that act model/backlog/backlog.yaml states that nothing was created in a tracker, and no task of this repository creates a work item (ADR-0029 decision 1). |
| Traces: adrs | ADR-0027, ADR-0028, ADR-0021, ADR-0029 |
| Depends on | AIFACTORY-US-378, AIFACTORY-US-379, AIFACTORY-US-380 |
| Sources | docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md, handoffs/2026-10-09-independent-review/INDEX.md, model/backlog/backlog.yaml, handoffs/2026-10-09-independent-review/open-items.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-155 Import of the backlog draft into Azure DevOps by the owner |
documentation | The owner imports the packed files in their order, or one increment file, into the root area of the project, which uses the Scrum process (decisions D81 and D85): Epic, Feature, Product Backlog Item, Task, with no area path column. Nothing is imported before the owner does it, and nothing in this repository creates a work item; the open row of the import in the handoff records is closed by the owner or stays open. | ConnectSoft.AI.SoftwareFactory.Documentation |
AIFACTORY-TASK-716 Verify owner-decisions against its acceptance criteria |
verification | The outputs of the tasks of AIFACTORY-FEAT-094 exist and python -I tools/docs_model validate reports no error, which proves AC1 to AC3 of AIFACTORY-US-135. |
ConnectSoft.AI.SoftwareFactory.Documentation |