DEVELOPER ENTRY

Build trustworthy multi-agent infrastructure together

TITMAS organizes specifications, adapter contracts, conformance, and reference-implementation boundaries into a discoverable, understandable, reusable developer entry.

Current stagePartially prepared · community not established

DEFINITION

What TITMAS is

titmas is the public developer entry for trusted multi-agent infrastructure; TITMAS remains its technical project identifier. Developers keep their chosen agent frameworks and runtimes; TITMAS focuses on portable identity, capability, execution, evidence, verification, and evaluation interfaces.

CONTRIBUTION SURFACES

Four infrastructure surfaces to build together

Specification

Rules

Define objects, fields, versions, ownership, and non-equivalence boundaries.

Adapter Contract

Mappings

Map observations from external agent runtimes into TITMAS boundaries.

Conformance

Claims

Test implementation claims with positive, negative, fail-closed, and result contracts.

Reference Implementation

Examples

Provide replaceable, reproducible learning paths without becoming the only runtime.

PROCESS

How a contribution moves

  1. 01Discover
  2. 02Choose a boundary
  3. 03Declare sources
  4. 04Prepare proposal
  5. 05Domain review
  6. 06Architecture decision
  7. 07Separate implementation authorization
  8. 08Conformance

PARTICIPATION

Who can participate

Human Developer

May prepare specifications, mappings, adapter contracts, tests, and documentation while owning source and result accountability.

Governed AI Agent

May assist with code, retrieval, tests, and citations; tools, sources, verification, and human accountability must be disclosed.

Reviewer Candidate

May identify boundary, compatibility, security, and failure issues. Review is not decision.

READY

What you can do now

  • Read bilingual architecture and machine status
  • Conceptually map your agent runtime to TITMAS
  • Review the minimum loop in the Technical Validation Pilot
  • Prepare a local proposal candidate without creating an external issue or PR

NOT YET

What you cannot do yet

  • Contribute to a GitHub organization that does not exist
  • Describe the contributor entry as an open community
  • Create agents, runtimes, permissions, or automatic authority
  • Claim external adoption, production readiness, certification, or a foundation

Public-entry migration status

Live nowhttps://redcrag.cn/
Future primary domaintitmas.cn · filing · not live
GitHub slugtitmas-cn · selected · organization not created
Repositories moved0 · each requires a separate decision

MACHINE-READABLE

Public resources that do not depend on GitHub