July 2025 | 13 meetings | ~10.1 hours of recordings
Q2 2025 was the quarter where planning became execution. Coming off the Dublin in-person TSC meetup in early April, the team immediately began working down the roadmap it had set: deprecating legacy components, building the APAP reference implementation, and onboarding five Google Summer of Code contributors — the most in the project’s history. The first live MCP integration with Claude shipped in May, OCI registries emerged as a distribution layer for smart legal contract artifacts, and Concerto’s long-incubating map types and import aliasing features were finally enabled by default. The quarter closed with GSoC contributors fully underway on all five projects.
Key Developments
- First live MCP/Claude integration. Dan’s May 7 demo showed Claude connecting via MCP to a locally running APAP server — querying templates, agreements, and triggering contract logic. This marked the first end-to-end LLM-to-smart-legal-contract integration in the project’s history.
- GSoC 2025 launched at record scale. Five funded projects — the most ever — kicked off in June: Concerto Linter, AI Assistant for Template Playground, Specification Conformance Tests, Decorator Command Set YAML converter, and Tailwind CSS UI redesign.
- APAP reference implementation shipped. The quarter saw APAP go from design to a running deployment at api.accordproject.org, with Postgres via Drizzle ORM, Docker Compose orchestration, and Auth0 integration for MCP OAuth delegation.
- OCI registries as artifact layer. Tim and the group converged on OCI registries as a vendor-neutral distribution mechanism for Accord Project templates and model artifacts, layered into APAP alongside Postgres.
- Concerto map types and import aliasing released. Matt’s PR removed the feature flags that had kept map declarations and import aliasing opt-in, promoting both features to standard in Concerto 3.22.
- Blockchain code generation. Martin demonstrated end-to-end generation of Rust ink! smart contracts from Concerto CTO files, deployed to Substrate — an early signal of Concerto’s multi-runtime reach.
Announcements
- Accord Project accepted for five Google Summer of Code 2025 projects (announced May 14)
- APAP reference implementation live at api.accordproject.org
- Concerto 3.22 released with map types and import aliasing enabled by default
- GSoC coding period begins June 2; all five contributors onboarded
- Nile’s MCP implementation transferred into the Accord Project GitHub org
Meeting Summaries
April 2 – TypeScript Template Logic
Dan demonstrated the new template-engine draft and trigger capabilities, allowing contract logic to be written in TypeScript and compiled on-the-fly. The group discussed Concerto-generated TypeScript types for type-safe template logic authoring and reviewed PR #1000 on semantic versioning policy.
April 23 – Agent Protocols, DeCombine SLC & Concerto
Post-Dublin, the group discussed supporting both MCP and Google’s Agent-to-Agent (A2A) protocol for exposing APAP capabilities to LLMs, agreeing to define concrete use cases before implementing either. Tim demonstrated de-combine-slc parsing Concerto payloads to configure Open Policy Agent policies within a state machine. Nile’s MCP implementation was agreed to be transferred into the Accord Project GitHub org.
April 24 – Deprecation Owners & App API Planning
The Dublin meetup’s invest/maintain/deprecate table was reviewed and owners were assigned — Jonathan on codegen, Sunkit on Template Playground, Tom on docs, Martin on AWS cleanup. Tim presented App API plans using Drizzle ORM with Postgres for CRUD over models, templates, and agreements, with authentication deferred in favour of a local Docker Compose setup first.
April 30 – Concerto, APAP Postgres, OCI Artifacts
Dan demoed Postgres support added to APAP using Drizzle ORM with schema auto-generated from the Concerto protocol model CTO file. Tim presented OCI registries as a vendor-neutral distribution mechanism for smart legal contract artifacts, demonstrating push and pull of Concerto payloads to Docker Hub using the CNCF ORAS tool.
May 7 – APAP MCP & OCI Artifacts
Dan showcased a working MCP integration connecting Claude to a locally running APAP server, using Auth0 for OAuth delegation to allow Claude to list templates, query agreements, and invoke convert-to-format tools — the first live demonstration of LLM-to-APAP integration.
May 14 – GSoC Projects & OCI Registry
Accord Project was accepted for five Google Summer of Code 2025 projects — the most ever funded. Tim presented the OCI registry proposal in full. Matt demoed a live APAP reference implementation deployed to api.accordproject.org with hosted Postgres, Nginx, and automated Docker Hub CI/CD.
May 15 – GSoC 2025 Contributor Kickoff
The five GSoC 2025 projects were formally introduced: Concerto Linter (Jamie/DocuSign), AI integration for Template Playground (Diana/Tim/Nile), Specification Conformance Tests (Dan), Decorator Command Set JSON/YAML converter (Sankit), and Template Playground Tailwind CSS redesign (Mahesh). Contributors introduced themselves from six countries.
May 21 – Concerto Feature Flags & MCP Tools
Matt presented a PR to fully release Concerto’s map types and import aliasing features by removing opt-in feature flags, targeting release in Concerto 3.22. Niall demonstrated an integration using the Ingest workflow orchestrator to connect an AI agent to the APAP MCP server, successfully querying contract agreement data.
May 28 – GSoC Projects & MCP Updates
Anshu (GSoC conformance tests) and Noel (APAP MCP) each reported progress — Noel adding resource registration and prompts support to the MCP server and exploring trusted execution environments on EC2. The two Template Playground GSoC projects were outlined: Ashot’s AI chat assistant and Mahesh’s Tailwind CSS UI redesign.
June 4 – Semver, Template Playground UI & AI Assistant
The group discussed Concerto versioning edge cases around 0.x-to-1.x upgrades. Mahesh presented a new minimalistic Template Playground UI mockup with togglable editor panels. GSoC contributor Asha demonstrated an AI assistant integrated into Template Playground with configurable LLM provider settings and prompt presets.
June 11 – Linter Rules, AI Assistant & MCP Security
Ahmed presented categorised Concerto linter naming rules as part of his GSoC project. Anshu demoed a working AI assistant supporting Google Gemini and OpenRouter. The team reviewed MCP security concerns including prompt-injection vulnerabilities via malicious tool schema field names, and noted ChatGPT’s new support for remote MCP servers.
June 18 – Concerto Decorators, YAML Format & Rust Codegen
Sanket proposed a Concerto feature to propagate decorators from type definitions to properties. Asma presented YAML conversion rules for the decorator command set. Martin demonstrated a Rust code generator that converts Accord Project CTO files into compilable Rust projects for running smart legal contract logic on a Substrate blockchain.
June 25 – Ink! Blockchain & Decorator YAML
Anshu presented GSoC progress on the Concerto conformance test repository, including semantic validation rules and a new CLI that generates testing project scaffolds. Martin demoed a workflow that generates Rust ink! smart contracts from Concerto CTO files and deploys them to a Substrate blockchain, with an off-chain listener producing PDF/Markdown outputs from on-chain events.
Plans & Upcoming Work
- GSoC midterm evaluations (mid-July) with contributor demo session
- Concerto Rust validator proof-of-concept (in-house, post-GSoC)
- APAP OCI registry integration
- Template Playground AI assistant and Tailwind CSS redesign (GSoC, summer)
- A2A protocol support investigation for APAP
- SemVer import ranges RFC (issue #931)