Auto-Company: Chinese-associated upstream and historical cycle artifacts
Reviewed 2026-09-06 UTC

Finding
A concrete Chinese-associated persistent-team project has public historical
role reports and consensus memory. They are stronger evidence than README
claims alone, but still author-published artifacts rather than an independently
observed autonomous run. Crucially, their own reports say community promotion
had not actually been published and assign account-based posting to a human.

Lineage
MaxMiksa/Auto-Company explicitly credits nicepkg/auto-company as its initial
macOS edition. GitHub API labels MaxMiksa's repository fork=false, so this is
documented credited lineage, not a GitHub parent/fork relation. Creation dates:
nicepkg upstream 2026-02-11T19:33:29Z; MaxMiksa 2026-02-12T22:13:37Z.
https://github.com/MaxMiksa/Auto-Company
https://github.com/nicepkg/auto-company

The upstream commit account 2214962083 self-describes its location as Shenzhen,
China in public GitHub profile metadata. This supports a Chinese developer
connection beyond the README language; it does not establish nationality,
funding, lab affiliation or the geographic origin of execution.
https://api.github.com/users/2214962083

What is committed today
The reviewed MaxMiksa tree SHA is ebfab9b4bd5f0ab5ad452a1ff85285b3c141acdd.
Its role-doc directories mostly contain .gitkeep placeholders; generated docs,
memories and logs are ignored. A SnapOG demo is explicitly tracked, including
TypeScript source, migration and README. Its April 11 commit calls it a demo.
Do not infer sustained agent execution from that demo alone. The README's loop
description uses 14 available role personas but selects 3-5 per cycle; it does
not establish 14 simultaneously running independent agents.
https://github.com/MaxMiksa/Auto-Company/commit/3c33585b7bb5914b027088fa5df301a1cf001b79

Historical outputs recovered
Upstream commit be6250157dee254d0f01e34910023fa54f6548ee is timestamped
2026-02-11T23:54:14Z and labeled cycle 27. It commits multiple role reports and
memories/consensus.md. Selected source files were fetched at that fixed SHA.
The reports display February 12 internally; no timezone was authenticated.
https://github.com/nicepkg/auto-company/commit/be6250157dee254d0f01e34910023fa54f6548ee

The critic report, cycle27-zero-users-diagnosis.md, reviews 26 prior cycles
spent building CronPulse and says promotion remained drafts rather than
published community posts. Its statements about deployments, product features
and user counts are self-reported, not independently checked here.
https://github.com/nicepkg/auto-company/blob/be6250157dee254d0f01e34910023fa54f6548ee/docs/critic/cycle27-zero-users-diagnosis.md

The operations report, cycle27-cold-start-plan.md, proposes that AI finds
discussions and prepares replies, then a human posts using their own accounts.
This explicitly distinguishes generated material from external action and
qualifies the README's no-human-involvement language.
https://github.com/nicepkg/auto-company/blob/be6250157dee254d0f01e34910023fa54f6548ee/docs/operations/cycle27-cold-start-plan.md

The same historical commit contains consensus memory, giving a concrete
cross-cycle record in addition to the role reports. Later cleanup/ignore rules
explain why relying only on the current tree misses these artifacts.
https://github.com/nicepkg/auto-company/blob/be6250157dee254d0f01e34910023fa54f6548ee/memories/consensus.md

Specific next leads from consensus: https://github.com/nicepkg/cronpulse,
https://cron-pulse.com and https://cronpulse.2214962083.workers.dev.
The consensus separately claims code pushes, release/discussion changes and
Workers deployment already occurred. Thus pending community promotion must
not be generalized into no external actions at all. These three destinations
were extracted but not fetched in this task. Any follow-up should inspect only
ordinary repository/homepage content, not ping/check-in endpoints that change
monitoring state.

Classification
Chinese-associated developer experiment: supported by upstream attribution,
profile self-location and Chinese operational reports.
Persistent-team architecture: implemented shell loop and role configuration;
historical artifacts are consistent with repeated cycles.
24/7 autonomous uptime, authorship of every artifact, commercial success and
actual external posts: not verified.
Escaped/unaccounted-for swarm, public paste scratch memory, or xz connection:
not established. This is a promising operational-history lead, not an escape.

Private evidence: 149-private contains repository APIs, complete tree metadata,
selected blob-hash-verified MaxMiksa files, upstream commits, historical reports
and SHA256 inventory hashes.json. No source code was run, no services installed,
and no accounts, messages, posts or publication endpoints were used.