docs(model-apps): sync the roadmap's spec-status section - #410
Merged
Akshay Maloo (akshaymaloo) merged 2 commits intoAug 14, 2026
Conversation
Copilot started reviewing on behalf of
Akshay Maloo (akshaymaloo)
August 12, 2026 17:15
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Docs-only update to keep the model-apps roadmap aligned with the external “MDA Agentic Authoring spec” status column, reflecting recent shipped primitives and correcting a stale reference.
Changes:
- Updated the spec evaluation date and corrected the “core P0 primitives complete” count from 8/10 to 9/10, aligning with the listed ✅ items.
- Replaced a dead branch pointer with
masterand added an explicit note to keep the roadmap and spec status column in sync going forward.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Two stale bits, both found while refreshing the MDA Agentic Authoring spec: - The "8 of 10 core P0 primitives" count was not updated when roles + JTBDs as first-class planning outputs (spec rank 1) shipped - the bullet list below it already said that was done, so the count contradicted its own section. Now 9 of 10, with rank 1 named in the list. - The pointer to branch `users/akmaloo/mda-spec-impl-status` is dead; that work merged, and the spec's status column now lives on master (refreshed today for ranks 1 / 14 / 29, which had been wrong since the persona work landed). Added an explicit "keep the two in step" note naming that drift, so the next person to flip a row here knows the spec column is a second place to update. Docs only - no behaviour change. Plugin suite 1427 pass. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 42626da2-b66f-4162-acaa-b1127ef23d89
Akshay Maloo (akshaymaloo)
force-pushed
the
users/akmaloo/roadmap-spec-sync
branch
from
August 14, 2026 16:02
dc98915 to
faf47ab
Compare
Copilot started reviewing on behalf of
Akshay Maloo (akshaymaloo)
August 14, 2026 16:02
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
plugins/model-apps/docs/app-builder-roadmap.md:106
- This line says the spec was last synced against "plugin v2.4.3", but the current model-apps plugin version in this repo is 2.4.4 (plugins/model-apps/.plugin/plugin.json). If the intent is to point readers at the current version, update the version here (or drop the version entirely to avoid frequent churn).
and **MCP server + Catalyst by default** (rank 12). The spec's §5 stack rank carries a status column annotated from
this roadmap; it is refreshed on `master` in `powerplatform-modelpages-ade` (last synced 2026-08-12, plugin v2.4.3).
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot started reviewing on behalf of
Akshay Maloo (akshaymaloo)
August 14, 2026 16:54
View session
Akshay Maloo (akshaymaloo)
enabled auto-merge (squash)
August 14, 2026 16:54
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
plugins/model-apps/docs/app-builder-roadmap.md:106
- The roadmap notes "plugin v2.4.3", but this repo's model-apps plugin.json reports version 2.4.4. This makes the sync note immediately stale/inaccurate for readers trying to correlate status vs a shipped version.
and **MCP server + Catalyst by default** (rank 12). The spec's §5 stack rank carries a status column annotated from
this roadmap; it is refreshed on `master` in `powerplatform-modelpages-ade` (last synced 2026-08-12, plugin v2.4.3).
davidkiz
approved these changes
Aug 14, 2026
This was referenced Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only sync, found while refreshing the MDA Agentic Authoring spec status column (pushed to that repo's
masterasbde4be5).Two stale bits in
docs/app-builder-roadmap.md:users/akmaloo/mda-spec-impl-statusmerged; the spec's status column lives onmasternow.I also added an explicit keep the two in step note. The spec's status column had ranks 1 / 14 / 29 wrong for ~2 weeks after the persona/security work landed (2026-08-03), because nothing connected "flip a row in the roadmap" to "update the column in the spec". Naming the drift is cheaper than rediscovering it.
On the spec side (separate repo, already pushed)
Each status change was verified against the plugin rather than inferred from this roadmap:
personas[]withjobs[]→privileges[]+surfaces[]; captured before the data model; plan-mode gatesecurityis one of the engine's 14 build phases; vendored bundle carriescreatePersonaRole/createSecurityRole/deleteSecurityRole/associateRecordsmodel-app-plan.mdrenders jobs→surfaces traceability, entity map, surfaces, access model per role, sample data, AI featuresRows left unchanged were re-checked, not assumed — e.g. rank 22 (rich AI descriptions) stays ❌ because the App Spec carries
descriptiononly onapp, and rank 16 (role-specific forms/views) stays ❌ because forms have no persona/role linkage. That evidence is now recorded in the spec footnote so the next pass need not re-derive it.Verification