About
About the methodology rather than about Accion Labs. The Accion Labs section is Practitioner.
What You Will Find Here
| Page | What it covers |
|---|---|
| Origins | The discovery story. The 2017 Breeze framework. The 2022 drug discovery moment. How the methodology came to be and how it took the name of its 2017 ancestor in the Breeze.AI platform. |
| Copyright and Trademark | The copyright notice on the methodology, the trademark policy on the term Semantic Engineering, fair-use guidance for analysts and academic publications. |
| Governance | How the methodology evolves. Who decides what enters the canon. Change log of methodology versions. How practitioners can propose extensions. |
| Contact | Press, analyst, and academic contact addresses. Routing for commercial inquiries to the Practitioner section. |
What the About Section Is Not
The About section is not Accion Labs’s company page. Accion Labs’s information lives in Practitioner > Accion Labs.
The About section is also not commercial. Commercial inquiries route to Practitioner > Contact.
The About section is for people who want to know what the methodology is, where it came from, who governs it, and how to cite it or contact someone about it in a non-commercial capacity.
Pick a page above, or return to the Home page.
Copyright and Trademark
The intellectual property posture of the methodology. The framework, principles, and concepts are public. The methodology mark is reserved.
Copyright
The Semantic Engineering methodology and the content on this site are copyright Accion Labs.
| Element | Status |
|---|---|
| The methodology framework (four-layer ontology, agent fleet patterns, custodianship discipline, layered team structure) | Copyright Accion Labs; publicly described on this site; freely reusable in accordance with the fair-use guidance below |
| The site’s specific content (text, diagrams, structural arrangement) | Copyright Accion Labs; reproduction in derivative works requires attribution |
| Source code in Accion Labs’s platforms (Breeze.AI, ASIMOV, ECL, KAPS, SPEX, Semantic KG) | Proprietary; not part of the public methodology |
Trademarks
Two terms are reserved trademarks of Accion Labs in the context of AI-assisted software delivery methodology.
- Semantic Engineering, the methodology name itself.
- Manual Translation Tax, the structural-cost framing used throughout the methodology to describe the everyday cost of converting unstructured knowledge into action.
The “Semantic Engineering” Trademark
The trademark policy:
| Use | Status |
|---|---|
| Referring to the methodology by name in analyst reports, academic publications, journalism, and similar editorial contexts | Permitted with no advance permission required, in the same way other named methodologies are referenced |
| Using “Semantic Engineering” as the name of a derivative methodology, consulting practice, or product | Not permitted without a license |
| Using “Semantic Engineering” in marketing material that implies official Accion Labs endorsement of a product or service | Not permitted without a license |
| Using “SE” as an abbreviation in editorial contexts | Permitted |
| Translating “Semantic Engineering” into other languages for editorial use | Permitted with attribution to Accion Labs |
In all editorial contexts the term should be capitalized as “Semantic Engineering” when referring specifically to the methodology, to distinguish it from the broader generic phrase “semantic engineering” which has been used in academic contexts for decades.
Fair-Use Guidance for Analysts
Industry analysts (Gartner, Forrester, IDC, and others) and academic researchers are encouraged to reference, summarize, and critique the methodology in their published work. The following uses are explicitly permitted without advance permission:
- Naming the methodology and Accion Labs as its primary practitioner
- Summarizing the four-layer ontology, the agent fleet, the enablement partnership, and other public elements
- Reproducing the diagrams from this site (mermaid sources are available on request) with attribution
- Citing specific pages on the site directly
- Critiquing the methodology, comparing it to alternatives, and reaching independent conclusions about its merits
The following uses require permission:
- Reproducing more than 500 words of verbatim content from the site in a single publication
- Reproducing the entire site or any major section as a standalone document
- Including the methodology in a paid vendor evaluation under a brand other than Semantic Engineering
For analyst inquiries about specific use, see About > Contact.
Fair-Use Guidance for Academic Use
Academic researchers may freely use the methodology in their work, including:
- Teaching the methodology in computer science, software engineering, and management curricula
- Using the methodology as a case study or example in academic papers
- Conducting independent research on the methodology’s effectiveness
- Comparing the methodology to other approaches in published comparative studies
Academic researchers who want to engage Accion Labs for primary-source interviews or access to engagement data should contact academic@accionlabs.com (a dedicated address for academic inquiries; see About > Contact).
Fair-Use Guidance for Practitioners
Independent practitioners (consultants, contractors, in-house engineers) may:
- Adopt the methodology in their own work
- Reference the methodology in client proposals and engagement materials
- Cite specific pages or papers in client communications
- Contribute patterns, refinements, and case studies through Accion Labs’s engagement-team channels
The following are not permitted without a license:
- Marketing oneself or one’s firm as offering “Semantic Engineering” as a branded service in competition with Accion Labs
- Using the methodology’s mark in a way that implies official Accion Labs certification or endorsement
The methodology is intended to be widely practiced. The trademark constraint is narrow and specific to commercial branding.
When a License Is Needed
A formal license from Accion Labs is required when:
- A firm wants to offer Semantic Engineering as a branded service under their own brand
- A product wants to use “Semantic Engineering” as part of its name or marketing positioning
- A training program wants to issue certificates that include the Semantic Engineering mark
- A book, course, or substantial work wants to use the methodology’s mark in the title
For licensing inquiries, write to licensing@accionlabs.com.
How This Posture Differs From Most Vendor Methodologies
Most vendor methodologies are either fully proprietary (the framework itself is not publicly documented) or fully open (the mark is not protected and the methodology has no consistent meaning).
The Semantic Engineering posture is intermediate. The framework is fully public so that the broader industry can adopt, critique, and extend the discipline. The mark is protected so that the term retains a specific, consistent meaning. The combination is closest to how the Toyota Production System is treated: the discipline is public; the named methodology has Toyota as its originator and primary practitioner.
This posture is chosen deliberately. A methodology that is fully proprietary cannot become an industry standard. A methodology whose mark is unprotected loses its specific meaning over time. The intermediate posture lets the discipline reach the widest possible audience while preserving the integrity of the name.
Continue to Governance for how the methodology evolves, or Contact for press and analyst inquiries.
Governance
The methodology evolves with the practice. This page describes who decides what evolves, how the decisions are made, and where the changes are documented.
Editorial Authority
The methodology is governed by an Editorial Board inside Accion Labs.
| Role | Responsibility |
|---|---|
| Editor-in-Chief | Final authority on changes to the spine of the methodology (the seven core sections of this site); arbitrates disputes; signs off on each version |
| Section Editors | Per-section editorial responsibility; review contributions affecting their section; coordinate with the Editor-in-Chief on changes that affect multiple sections |
| Custodianship Editor | Specific authority over the Enablement Partnership and its contractual frame; coordinates with Accion Labs’s legal function on any change with contractual implications |
| Methodology Steward | Operational owner of the canon; maintains the change log; coordinates with the Practitioner Community on contributions |
The Editorial Board meets monthly. Changes that affect the spine require Editor-in-Chief sign-off. Changes within a section can be approved by the Section Editor. Contributions from the community route to the Section Editor first.
What Counts as a Methodology Change
Three categories of change are tracked.
| Category | Examples | Cadence |
|---|---|---|
| Spine changes | Adding or removing a top-level section, renaming a core concept, modifying the four-layer ontology structure | Rare; requires Editor-in-Chief sign-off and is announced in the newsletter |
| Depth-page changes | Adding a new depth page, substantially revising an existing one, adding a new pattern or case archetype | Quarterly; tracked in the change log |
| Editorial updates | Wording refinements, link updates, glossary additions | Continuous; minor changes do not require formal sign-off |
The Change Log
Every spine and depth-page change is recorded in the change log with date, description, author, and Editorial Board reviewer.
A summary of recent changes:
| Version | Date | Notable changes |
|---|---|---|
| v1.0 | June 2026 | Initial public release of the methodology site |
| (Future versions will be logged here as the methodology evolves) |
How Practitioners Propose Extensions
Three paths for a practitioner to contribute to the methodology.
| Path | Use case |
|---|---|
| Direct contribution | A specific pattern, refinement, or case study; submitted through Accion Labs’s engagement-team channels |
| Editorial Board proposal | A spine-level change (renaming a concept, restructuring a section); submitted by writing to methodology@accionlabs.com |
| Industry alignment proposal | A change that aligns the methodology to broader industry vocabulary (e.g., a Snowflake or Palantir terminology shift); submitted as an Editorial Board proposal with the industry context attached |
Submissions are acknowledged within two weeks and routed to the relevant Section Editor. Standard review is four to six weeks. Spine-level changes can take longer because they often require coordination across multiple section editors.
Versioning Policy
The methodology uses semantic versioning at the spine level.
| Version bump | Meaning |
|---|---|
| Major (v1 → v2) | Spine restructure that breaks reading paths; rare; reserved for fundamental shifts in how the methodology is organized |
| Minor (v1.0 → v1.1) | New depth pages, substantial revisions to existing pages, new sections within the spine; quarterly |
| Patch (v1.0 → v1.0.1) | Editorial refinements, link fixes, glossary additions; continuous |
The change log records the version bump for each change. Subscribers to the newsletter receive notification of major and minor changes; patch-level changes are visible in the change log but are not separately announced.
How Conflicts Are Resolved
When two contributors propose conflicting changes, or when an existing pattern is challenged by a new pattern, the Editorial Board adjudicates. The decision-making frame:
- Does the new pattern survive across multiple independent engagements? Patterns from a single engagement are too narrow to enter the canon.
- Does the new pattern align with the methodology’s structural commitments? Patterns that violate the aperture discipline, the partition rule, or the custodianship principle are not adopted.
- Does the new pattern improve clarity, reduce ambiguity, or enable new capability? Patterns that add complexity without adding value are not adopted.
- When the new pattern conflicts with an existing pattern, which is more deeply embedded in the methodology and the existing engagements? Conflicts default to preserving the embedded pattern unless the new one is meaningfully better.
The Editorial Board’s decisions are recorded in the change log with the reasoning. Dissenting opinions from board members are also recorded where they are substantial.
Independence From Commercial Pressure
The Editorial Board is structurally separated from Accion Labs’s commercial account teams. Editorial decisions are not influenced by client requests, account-level commercial pressure, or sales conversations. The independence is what protects the methodology from drift toward whatever is convenient for the largest client.
This separation is part of the The Enablement Partnership discipline’s Duty of Loyalty. The methodology serves practitioners and clients broadly; it does not serve any individual client at the expense of the methodology’s integrity.
How to Audit the Methodology’s Governance
For analysts and academics who want to verify that the governance is real:
- The change log provides the full history of canonical changes
- The Editorial Board membership is published on the Practitioner > Accion Labs page
- The methodology mark and the trademark policy are documented in Copyright and Trademark
- The Engagement Council, which holds the firewall between competing-client engagements, has its membership and charter publicly available on request
For audit requests, write to methodology@accionlabs.com.
Continue to Contact for press, analyst, and academic inquiries.
Contact
Non-commercial contact for the methodology. For commercial inquiries (workshops, engagements, pricing), see Practitioner > Contact.
Press
For journalism, podcast appearances, and commentary requests:
press@accionlabs.com
Include your name, publication, and the angle you are exploring. Response within two business days. For embargo requirements, note the date and time in the subject line.
The methodology’s named spokespeople include the Editor-in-Chief and selected senior practitioners. Specific spokespeople are assigned per request based on the angle.
Industry Analysts
For analyst inquiries (Gartner, Forrester, IDC, others):
analyst@accionlabs.com
Include your firm, role, and the specific analysis you are working on. The analyst relations team coordinates briefings, deep-dive sessions, and ongoing inclusion in vendor evaluations. Response within two business days.
For ongoing analyst coverage, request to be added to the analyst briefing distribution list, which includes:
- Quarterly briefing on methodology evolution
- Notification of new papers
- Access to engagement metrics under appropriate NDAs
- Priority on briefing requests when major methodology updates are released
Academic Researchers
For academic research, teaching use, and primary-source interviews:
academic@accionlabs.com
Include your institution, role, and the specific research or teaching context. Academic engagements typically include access to anonymized engagement data, interviews with senior practitioners, and reciprocal arrangements where the methodology’s evolution benefits from the research output.
Methodology Governance
For editorial questions, contribution proposals, and methodology-level discussions:
methodology@accionlabs.com
Routed to the Methodology Steward, who coordinates with the Editorial Board. Response within two weeks.
Licensing
For licensing inquiries (using the Semantic Engineering mark in a derivative product or service, branded training programs, etc.):
licensing@accionlabs.com
See Copyright and Trademark for the licensing posture and the cases that require a license.
Community
For community participation, contribution submissions, and newsletter subscription:
community@accionlabs.com
Commercial Inquiries
Commercial inquiries (workshops, engagement scoping, pricing, RFPs) route to the Practitioner section. See Practitioner > Contact for the right addresses.
What This Page Does Not Do
This page does not handle:
- Workshop requests (see Practitioner > Contact)
- Pricing inquiries (see Practitioner > Contact)
- Existing engagement support (contact your engagement lead directly)
- Recruitment inquiries (see Accion Labs careers, not part of this site)