Release record | 25 August 2026

PALO 3.1 and PALO-AI 2.7 release verification record

This page records the source revision, automated validation results, published artifacts and current maturity limits for the PALO 3.1 and PALO-AI 2.7 public baseline dated 25 August 2026.

Scope: This record reports repository artifacts and automated checks. It is not an independent security assessment, certification, legal determination, compliance conclusion or production authorization.

GitHub Actions run 32828014857 Pull request #29 Release manifest Production readiness

Baseline identity

Version, revision and merge references used for the observations on this page.

PALO Web: 3.1.0Released 23 August 2026
PALO-AI: 2.7.0Developer preview | 25 August 2026
Baseline commit: a8673d2a472108c7b1d8a056c3a6af9962687bee
Pull request: #29Merged 25 August 2026 | CI run

Automated verification results

Each row separates the method, observed baseline result, supported interpretation and excluded interpretation.

Observations from commit `a8673d2` and the named queries on 25 August 2026.
Area	Method	Baseline result	What it establishes	What it does not establish
Agentic contracts and policy	`npm run validate:agentic`	21 contracts; 38 MCP tools; OPA compile and policy tests passed	The pinned contract set was parsed and checked, the MCP tool inventory was counted, and the bundled OPA policy compiled and passed its automated tests.	Organization-specific production-policy ownership or connector non-bypassability.
Runtime tests	`npm run validate:agentic`	68 Node tests passed; 3 Dify tests passed	The tested reference-runtime and Dify integration paths returned their expected results on the named baseline.	Independent penetration testing, multi-replica behavior or production operating effectiveness.
Authoring source	`npm run validate`	37 source HTML files; 31 controls; 38 indicators; 6 gates; 11 sources; 6 cases; 5 templates	The configured authoring-source inventories and structural validations completed for the named baseline.	Certification, legal completeness or adopter implementation.
Publication build	`npm run build` `npm run validate:dist` `npm run build:check`	321 allowlisted source files; 95 built HTML files; exact dist inventory of 391 files	The build used the configured allowlist and the resulting distribution matched the expected inventory for this baseline.	Equivalence with a later uncommitted or independently rebuilt artifact.
Browser smoke	`npm run smoke`	94 public HTML pages plus named evidence, Platform Map, Library, Governance Hub and responsive flows	The named pages and flows loaded and met the scripted smoke assertions in the test environment.	Exhaustive browser, accessibility or usability coverage.
GitHub Actions	Workflow run 32828014857	Run 32828014857 completed successfully; windows-build, build and deploy jobs passed	The pinned hosted workflow recorded successful completion for all three named jobs.	External audit or production deployment assurance.
GitHub dependency alerts	GitHub Dependabot and secret-scanning API queries	0 open Dependabot alerts and 0 open secret-scanning alerts when queried on 25 August 2026	The GitHub APIs returned no open alerts in those two categories at query time.	Absence of vulnerabilities. The repository has no CodeQL analysis result; the API returned `no analysis found`.
Package-lock audits	`npm audit --package-lock-only` against the named locks	0 vulnerabilities reported by npm audit --package-lock-only for root, Governance Hub, n8n runtime package and isolated n8n tooling locks on 25 August 2026	The npm advisory service reported no matched vulnerability for dependencies resolved by those lockfiles at query time.	Source-code security, exploitability analysis or future dependency status.

All numerical results are dated observations for the named revision or query. They are not continuous guarantees about later commits, deployments or advisory data.

Negative-test coverage

Selected denial, invalidation, replay and tenant-isolation cases present in the pinned test sources.

Authority Context 1.4 rejects untrusted issuers and delegation windows that do not cover the live claim.
data-assurance.test.js:226
Cached authority is revalidated instead of returning a prior allow.
assurance.test.js:102
Continuous-assurance signals invalidate Data Fitness and revoke matching unused capabilities.
data-assurance.test.js:298
OIDC tenant binding covers Action Claim 1.3 and 1.4 tenant locations.
production-admission.test.js:28
Replayed disclosure observations and post-effect disclosure-receipt failures open held/inconclusive incidents without persistent row payloads.
data-assurance.test.js:263 data-assurance.test.js:289
Tenant-aware incident lookup excludes unscoped legacy records from OIDC results.
data-assurance.test.js:329

Published artifacts and checksums

The tagged web archive and later main-branch baseline have different identities. Their digests are recorded separately.

Tagged PALO Web v3.1.0 Hostinger archive

The public tagged PALO Web v3.1.0 Hostinger archive belongs to commit b79fc1056d7e403698ffe2381a97dd689a8d8111.

Filename: PALO-Hostinger-3.1.0.zip
SHA-256: f33b272414a6df25eb0b7a6933eb32ab155ee6e546b1de66e8ed17b22ca6aa2b
Size: 57,407,719 bytes

Artifact boundary: The later main-branch PALO-AI 2.7 and site changes are not the same artifact as the tagged v3.1.0 archive. A rebuilt current-site archive must be published under a distinct release identity and checksum. This page therefore does not present a local unpublished archive as the historical tagged artifact.

Pinned main-branch baseline files

The following two digests were calculated from commit a8673d2 before publication of this verification page. They do not hash a future deployment that contains this page.

release-manifest.json: 0b1824b8a12f2dc43b6ac9b5d723565f0f16cb66214b56aff3b0b5406de54716
Root package-lock.json: 1f4b02211bf9f7ee12514a896fa7341eb8b436ddb73aa1b7813da9f1c1da513b

Independent reproduction

Commands and environment prerequisites for running the repository P0 sequence at the pinned revision.

Prerequisites

Node 22 and npm
Python 3
Network access for pinned dependencies
A Chromium-capable environment

npm run p0 installs the Governance Hub lockfile, checksum-verifies OPA, validates contracts, policies, runtime, connectors and authoring source, builds deterministic dist, checks its exact inventory and runs browser smoke.

git clone https://github.com/sev7enITA/PALOframework.git
cd PALOframework
git checkout a8673d2a472108c7b1d8a056c3a6af9962687bee
npm ci
npm run p0

.github/workflows/deploy.yml scripts/validate-agentic.mjs scripts/build.mjs scripts/browser-smoke.mjs

Current maturity limits

Repository state and the additional production evidence identified for each area.

Area	Current repository state	Required production evidence
Capabilities	40 tracked capabilities; 5 implemented, 28 prototype, 7 specified, 0 production-ready.	Deployment-specific implementation, operating-effectiveness results and accountable admission records for every applicable capability.
Reference persistence	SQLite, single instance, in-process recovery.	Production database, high availability, durable work, backup/restore and RPO/RTO evidence.
Keys	Process-held/HMAC reference mechanisms.	KMS/HSM, rotation, revocation and custody separation.
Tenancy	Token/claim checks exist; no storage-level multi-tenant isolation.	Tenant-separated storage, encryption and negative isolation assurance.
Connectors	Reference in-process connectors and assertions.	Isolated, allowlisted or remotely attested non-bypass connectors.
Exactly-once	Not universally claimed.	Distributed coordination, idempotency and failure/recovery evidence.
Evidence	Selected tamper detection within the same host/key boundary.	Independent anchoring or custody and external assessment.
Operations	Incident lifecycle prototype.	Enterprise incident operations, SIEM, retention/legal hold and tested recovery.
Assurance	No independent production security or cryptographic assessment is bundled.	Independent assessment with documented scope, findings, remediation, retest and accountable residual-risk decisions.

Capability Matrix Production Readiness Security overview Security policy

Development-method disclosure

Scope of the authorship information recorded by repository history and by this page.

The repository has been developed with AI-assisted engineering and documentation tools under human direction and review, alongside conventional development, testing and version-control tooling. Commit history records repository authorship and change integration; it does not demonstrate that every task was performed without assistance. This verification record evaluates published artifacts and automated checks, not unaided authorship.