Releases: judeper/FSI-AgentGov-Solutions
Releases · judeper/FSI-AgentGov-Solutions
v1.4.1 - solutions.json controls/dependencies/status
Added
solutions.jsonnow includes per-solutioncontrols,dependencies, andstatusfields (additive — schemaVersion bumped to 1.4.1 per the additive-only policy). Customers and downstream tools consuming the lock file can now see control mappings without crawling individual manifests.
Notes
- No manifest changes required; existing
manifest.yamlfiles already carried these fields. Only the projection inscripts/build-manifest.pywas extended.
v1.4.0 - Manifest unification
Manifest unification + alignment with FSI-AgentGov v1.4
Replaces the centralized scripts/solution-config.yml with per-solution manifest.yaml files and adds a committed root-level solutions.json consumable by the framework's refresh_solutions_lock.py.
Added
<solution>/manifest.yamlfor all 35 solutions (canonical id = folder name; required fields:id,name,description,version,status,domain,tier,controls,url,prerequisites,verification).scripts/manifest.schema.json— JSON Schema (Draft 2020-12) enforcing the per-solution manifest contract.scripts/build-manifest.py— single generator forsolutions.json, README catalog table (between<!-- BEGIN:SOLUTIONS -->markers),site-docs/solutions/index.md, all 35 detail pages,site-docs/reference/control-mapping.md(lists ALL 78 framework controls), and the home-page hero metrics block. Supports--checkfor CI drift detection.solutions.jsonat repo root, exposed athttps://raw.githubusercontent.com/judeper/FSI-AgentGov-Solutions/v1.4.0/solutions.json..github/workflows/manifest-check.yml— PR gate that fails when manifests reference unknown framework control IDs or generated artifacts drift from manifests. Pins frameworkcontrols.jsonvia the v1.4 branch.
Changed
- 6 solutions previously linked to GitHub blob URLs from sidebar nav now have rendered detail pages:
cross-tenant-external-sharing-governance,agent-knowledge-source-scanner,hitl-workflow-governance,model-risk-management-automation,credential-oversharing-detector,agent-365-lifecycle-governance. - Display-name normalization:
Segregation of Duties Detector,Agent Access Governance Monitor,MIME Type Restrictions for File Uploads,Hallucination Feedback Tracker,Conflict of Interest Testing. compliance-dashboardcontrols now include3.4(Incident Reporting and Root Cause Analysis).agent-observability-foundationcontrols populated:1.7, 2.8, 2.9, 3.2.action-confirmation-auditorcontrols corrected to2.12, 1.10.- Pillar 4 control mapping page now lists all 9 SharePoint controls (4.1–4.9); previously listed only 4.3.
- Coverage Summary on control-mapping page now reads from manifest data (35 solutions).
scripts/publish_docs.ymland the docs build pipeline both invokebuild-manifest.pyinstead ofbuild-docs.py.
Removed
scripts/solution-config.yml— superseded by per-solution manifests.scripts/build-docs.py— superseded byscripts/build-manifest.py.
Schema evolution policy
solutions.jsonschema 1.4.x is additive-only. New optional fields are allowed in 1.4.1 and later patch/minor releases. Field renames, new required fields, or shape changes (e.g., turning a string into an array) require 1.5.0 with a coordinated framework update so that consumers (currentlyjudeper/fsi-agentgovlock-refresh tooling) upgrade in lockstep.
Stability guarantees
- No solution folder renamed. All
/<folder>/paths in the repo are unchanged. - No
/solutions/<folder>/URL changed on the public site. Detail pages stay atsite-docs/solutions/<folder>/index.md. - Sidebar nav entries that previously pointed at GitHub blob URLs now point at internal pages with the same human-visible labels — no link redirects required.
Verification
python scripts/build-manifest.py # idempotent regen
python scripts/build-manifest.py --check # exits 0 only when in sync
mkdocs build --strict # site builds cleanAfter tagging, the framework's refresh_solutions_lock.py --tag v1.4.0 consumes solutions.json from the raw GitHub URL.