Skip to content
View Cornelius-Chen's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report Cornelius-Chen

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Cornelius-Chen/README.md

Rongrong Chen · Cornelius

I design AI systems that can learn from work, use tools within human authority, and show the evidence behind a result.

M.A. Statistics, Columbia University · expected 2027 · LinkedIn

Illustrated research studio with Cornelius at the center and design, market, media, and system workstations around him

The research studio illustration is the portfolio cover. The map below explains the project relationships.

The architecture I am building

Jervis is the center of this research portfolio. It asks how a model can turn examples, practice, and feedback into scoped, reusable domain judgment—and how a later task can test whether that judgment actually helps. I set the system goals, boundaries, and acceptance criteria; the models and tools are replaceable workers inside that design.

Start with the research: Jervis learning architecture · Puretelligence trader research · SpecMirror engineering review · system boundaries

Illustrated systems map with Jervis and nested Designer at the center, Puretelligence and SpecMirror alongside, and separate local model and tool pipelines

An illustrated map of responsibility and bounded handoffs. The lower pipeline and supporting systems remain separate experiments. Open the full illustration · Inspect the editable technical map · Read the architecture thesis

Architecture decision Observed local behavior Evidence limit
A candidate has to survive scope selection. Jervis reused one Designer judgment on a new brief and rejected a narrower judgment on another. The model comparison was mixed; human quality gain remains unverified.
Market facts and trader experience have different owners. Puretelligence's underlying Guanlan system supplied time-bounded evidence and simulation; Jervis retained candidate experience for a continuing trader identity. Historical simulation did not establish profitable live trading.
Completion and acceptance have separate records. SpecMirror displays scoped runs and their evidence at the engineering node. A full human-feedback-to-learning cycle has not been demonstrated.

Question. Can a judgment survive one task, remain bound to its source and scope, and be evaluated on a later task? Designer is Jervis's first domain apprenticeship. Mission holds the work graph; Registry and EventLog preserve versions and transitions; replaceable workers receive bounded WorkOrders.

Illustrated Jervis research experiment showing versioned judgment, conditional selection, partial rebuild and stale result rejection

Observed. An offline replay stores one experimental Designer judgment, selects it for one fresh brief, rejects it for another, commits both pages and checks browser behavior. A separate composition run rebuilds dependent artifacts after a shared fact changes and rejects a stale worker result. Fixed synthetic responses make these reproducible mechanism tests. Limit: historical model comparisons were mixed; human-rated capability gain remains unverified. Research case and source evidence →

Question. Can a trader revise experience without leaking later outcomes into an earlier decision or collapsing selling, buying and switching into one action? Puretelligence presents the research architecture built in Guanlan. Its market system owns point-in-time facts and simulation; Jervis owns candidate experience; Lu Dongyangzi is the continuing trader identity.

Illustrated Puretelligence research experiment showing the decision cutoff, independent actions, later diagnosis and unpromoted candidate

Observed. The historical local study completed diagnostic cases, targeted study and new-material retests, leaving a candidate revision unpromoted. The public source release runs invented market paths through the original replay modules; a separate bridge checks exact Jervis Registry versions and source attachments before a fixed-action retest. Limit: the public fixtures do not replay the private worker, establish a blind gain, or show live fills. Research case and evidence boundary →

Question. Can one editable project detail become scoped agent work whose exact changes return to the same node for human review? The public tests cover two segments: a feedback-to-exact-run service/UI path, and a separate dual-agent service path with isolated claims, artifacts, token deltas, review calls and persistence after restart.

Illustrated SpecMirror engineering mechanisms showing exact opinion-to-run binding and a separately tested two-agent service path

Limit: the two paths have not been joined into one live autonomous run with a real human acceptance. Engineering details → · English UI evidence →

In a separate DeepSeek Harness experiment, Qwen 3.5 9B is the active local agent and vision model; Qwen 3.8 27B is a recorded quality alternate removed from local routing. One MCP path carries a Qwen-Image-2.1 first frame into an asynchronous MiniMax H3 image-to-video job, with a completed same-job MP4 and receipt. Another narrows Cua Driver to seven bounded Computer Use tools and requires observe → act → verify. The public source and evidence include both wrappers, offline contract checks, the actual media pair and a redacted deterministic Notepad run. These pipelines are not a verified Jervis backend. Architecture and limits →

Illustrated local model, media and Computer Use pipelines with an inactive 27B alternative and bounded driver-session recovery

A separate, runnable local mission controller owns scoped tools, budgets, human approvals, verifier steps, and event history. Its public demo uses a scripted model, so it demonstrates the control boundary rather than real-model performance. Run the offline mission →

Smaller runnable systems

Repository What it demonstrates
API Hub Capability grants, provider credential custody, dry-run calls, usage, and audit in a local MVP.
AttentionOS A decision record that freezes original evidence and compares it with later outcomes.

The public repositories contain selected source and explanations. Ongoing local research, credentials, market datasets, private feedback, and full runtime records are not included in these releases.

Earlier relationship sketch (historical names and simplified links)

Pinned Loading

  1. Jervis Jervis Public

    Runnable architecture slice: source-bound learning, persistent state, scoped Designer judgments and work-order commits

    Python

  2. Puretelligence Puretelligence Public

    Guanlan's point-in-time A-share research architecture, synthetic decision replay, and Q1-Q5 evidence boundaries

    Python

  3. SpecMirror SpecMirror Public

    Engineering review at the original feedback node, with exact run/source evidence and human acceptance boundary

    TypeScript

  4. Cornelius-Chen Cornelius-Chen Public

    Rongrong Chen | runnable AI systems, architecture thesis, and research notes