Lanruan IntelligenceLANRUAN INTELLIGENCE03 / AI project collaboration
EGC
An append-only governance ledger for AI-assisted development: see what was decided, who reviewed it, and what still stands.
Core governance available · Web multi-project access and licensing in developmentDecisions, changes and review notes pile up in long documents until nobody can say which conclusion is still current.
When several coding assistants work in parallel, it's hard to reconstruct who changed what, why, and whether anyone checked it.
Opening each project one by one is slow, and blockers or conflicting decisions slip through.
Nothing is edited or deleted; new events supersede old ones, every current conclusion points to its source, and a hash chain exposes tampering.
Reviews are their own records, no one approves their own work, and anything awaiting review or changes lands on the open-items list automatically.
The command line for developers and automation, MCP for AI coding assistants, and a web workspace for business, audit and management teams.
Who: Engineering leads running several AI coding assistants at once. Situation: Assistants change code in parallel, and afterwards no one can say who did what, why, or whether it was checked. How: Assistants connect via MCP, log an event before starting, mark it Implemented when done, and a different identity reviews it. Outcome: Every change carries a record, a rationale and an independent verdict; anything unreviewed, sent back or blocked shows up as an open item.
Who: Project owners and engineering directors responsible for several projects. Situation: Each project has its own ledger; opening them one by one is slow and risks are hard to compare. How: Register each ledger with the multi-project hub to search topics, open items and conflicting decisions in one place (available through developer tools today; the web dashboard is in development). Outcome: One place to see the whole portfolio and spot stalled projects and contradictory decisions fast.
Who: Quality and release managers, internal and external auditors. Situation: Before a release or handover, you must confirm every key change was reviewed—and be able to prove it. How: Check unclosed reviews, blockers and conflicts, verify ledger integrity, and export a governance report (report export is in preview). Outcome: Audit material traceable to every source event, with any tampering detected.
Every entry point writes through one authenticated path and rule checks into the ledger; the hash chain and indexes feed derived views back to each entry point, and ledgers sync read-only into the multi-project hub.
From logging to independent review. Preview features may change before general release; dates for in-development features will be announced separately. EGC provides traceable audit evidence; it does not constitute any compliance certification.
Before starting, check validation results, open items, recent events and milestone progress.
Log a draft event for the change.
Append progress as you go, then mark it Implemented.
A reviewer other than the author approves or requests changes; requested changes are fixed and resubmitted.
Once approved, current conclusions and milestone progress update automatically.
When a new decision arrives, a new event supersedes the old one and the full history stays intact.
Arrows show only the provenance of registrations, review records and derived views; they do not mean that EGC executes work or grants approval automatically.
Records every change, decision and review as append-only, traceable events, deriving views of “what applies now, what remains to be done, and who reviewed it”.
EGC does not execute code for you, schedule AI tasks, or replace people in making the final confirmation. Your chosen tools or team decide who does the work; EGC records what happened clearly and keeps reviews independent.
AI coding assistants connect via MCP, scripts via the command line, and people view and review through the Web workspace (the multi-project workspace is in preview); all three entry points write to the same ledger and follow the same rules.
If your team needs execution controls such as “only one executor at a time” or “human confirmation required at key steps”, you can use EGC alongside Lanruan’s EGC Supervisor (see its product page for the status and public description of EGC Supervisor).
Explore EGC Supervisor| Dimension | EGC is responsible for | Outside EGC’s scope |
|---|---|---|
| Records | Append-only events, reviews and relationships | Modifying or deleting history |
| Reviews | Separation of reviewer and author; traceable review conclusions | Automatically approving its own changes |
| Views | Current conclusions, open items, mainline progress and multi-project summaries | Real-time push (currently retrieved by refreshing) |
| Execution | Recording execution results | Scheduling, running or assigning execution tasks |
EGC handles records and reviews; execution is carried out by the tools or team you choose.
Up to 3 projects, 200 events per project
Free
Purchasing not yet availableUp to 10 projects, 1,000 events per project
US$19.9/year overseas; ¥119/year in mainland China
Purchasing not yet availableUnlimited projects, 10,000 events per project; includes all advanced features
US$59.9/year overseas; ¥359/year in mainland China
Purchasing not yet availableUnlimited projects and events; team collaboration and support tailored on request
Contact us
Purchasing not yet availableOne license activates one machine, and every project on that machine shares the same edition; event quotas are counted per project. Advanced features (Functional DNA, governance automation, intelligent recommendations and bulk remediation, AI model and agent management, release and delivery gates) are available from Medium upward. Annual billing only. Purchasing is not yet available; prices are subject to the final checkout page.
The following interfaces are product previews (not released). All projects and data shown are fictional demonstrations and do not represent product outcomes.
