Codetown ::: a software developer's community
Class Family Accord - Abstract
An Accord class family is a hierarchy of classes for which another class hierarchy has been designated as corresponding. Class A0 is the top of the class family, class A1 extends A0, class An extends An-1.
The partner of this class family is B0 at the top, Bn extends Bn-1. Class family A and B are have an Accord relationship if, by design intention, An corresponds to Bn. In each level, there is at least one method that overrides or defines a variant with a behavior representative of the progression of requirements.
The intention of this design concept is to maintain this correspondence when, as requirements evolve, the design calls for extending An and Bn into An+1 and Bn+1. The reason for maintaining this relationship would be that A has new or refined behaviors that only make sense with reference to the state or behaviors of B at the same level.
To realize this relationship in the Java programming language, a designer could simply document the intention. However, coding would inevitably require explicit down cast to force references to the intended levels. This white paper suggests a set of Java annotations to make the Accord relationship between class families explicit and generate the necessary dispatch code and casts. The resulting generated code would in effect provide a parametric override capability.
At a minimum an annotation @Accord designates a class as the head or subclass in a class family. Its attribute has an attribute, partner, to identify the other class family. Methods that are intended to follow the progression are annotated as @Covariant. The effect is to make the method be a covariant override. Its parameter referring to a class at the same inheritance level in the partner family is treated a covariant. A prototype precompiler is (to be) provided for research purposes.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

As organizations scale, communication overload, loss of shared context, and trust gaps emerge, Charlotte de Jong Schouwenburg mentioned. Trust must be built team by team; it can’t be replicated. Trust is interpersonal, while psychological safety is among people and fuels learning. Leaders must deliberately design structures, rituals, and metrics that reward transparency and cohesion at scale.
By Ben Linders
GitHub will use Copilot interaction data from Free, Pro, and Pro+ users to train AI models starting April 24, opting in by default. Collected data includes code snippets, inputs, outputs, and navigation patterns from active sessions, including private repos. Business and Enterprise tiers are excluded. Community concerns include dark patterns, IP exposure, and GDPR compliance.
By Steef-Jan Wiggers
Adrian Cockcroft explains the transition from cloud-native to AI-native development. He shares his "director-level" approach to managing swarms of autonomous agents using tools like Cursor and Claude Flow. Discussing real-world experiments in BDD, MCP servers, and language porting, he discusses why the future of engineering lies in building platforms that orchestrate AI-driven development.
By Adrian Cockcroft
This article introduces Context-Augmented Generation (CAG) as an architectural refinement of RAG for enterprise systems. It shows how a Spring Boot-based context manager can incorporate user identity, session state, and policy constraints into AI workflows, improving traceability, consistency, and governance without altering existing retrievers or LLM infrastructure.
By Syed Danish Ali
ESLint version 10 has removed the legacy eslintrc configuration system, finalizing a long transition to flat config. The update enhances developer experience, especially for plugin authors and monorepo teams, by changing configuration file location and improving JSX reference tracking. Node.js support has been tightened, and new assertion options have been added to the RuleTester API.
By Daniel Curtis
© 2026 Created by Michael Levin.
Powered by
You need to be a member of Codetown to add comments!
Join Codetown