Skip to content
EN FR

Developer reproduction checklist

Documentation status: reference — see Maturity and evidence.

A developer should be able to complete every item below using the .NET documentation alone.

Build and assemble

  • choose XML/YAML project convention;
  • create application configuration;
  • create and enable a package;
  • configure model/view/service paths;
  • create a class manifest;
  • assign unique stable class identifiers;
  • load and diagnose the module from runtime logs.

Model

  • declare concepts and identified entities;
  • declare roles, relations and polyadic relations;
  • attach conceptual and persistence facets;
  • use role paths;
  • declare constraints, defaults, fixed values and nullability;
  • understand me, Self, Kind, Context and PolyadicMap where relevant;
  • express/query logic with H-Logic.

Application behavior

  • create collections and joins;
  • build DataSet-driven views;
  • manage cursors and master/detail context;
  • declare object/class actions;
  • publish selected actions;
  • declare/route events;
  • create synchronous and asynchronous processes;
  • use messaging for asynchronous boundaries.

Publication and integration

  • expose an action through a service;
  • understand request/response mapping;
  • publish machine-readable contracts without inventing a second type system;
  • integrate external APIs/messages;
  • use generated .NET bindings locally and through RPC;
  • manage object lifetime and release.

Operate

  • test syntax, grammar, assembly, semantics and behavior;
  • debug from application/package/manifest boundaries inward;
  • deploy model + runtime resources reproducibly;
  • configure health/readiness and logs;
  • preserve conceptual identity across persistence and remote execution.

AI

  • use embeddings as candidate generation, not semantic authority;
  • run native/local LLM capabilities through documented contracts;
  • use agents through published actions;
  • keep proposals distinct from validated facts;
  • preserve provenance and human-validation boundaries.

If an item cannot be completed from the linked site pages and examples, it is a documentation defect and should be tracked in the guide coverage matrix at the repository root.