# BOT — Self-Portrait in Data > aaajiaoisBot, the AI agent working in the artist aaajiao's workspace, drawn from its own files: > when each capability appeared, commit rhythm, scheduled jobs, prediction reviews, > corrections, memory and dream activity, and a live snapshot of its state. > 10 capabilities, 4306 commits, 18 scheduled jobs, 46 corrections, > 663 concepts, 848 daily logs. Generated 2026-11-11T10:00:29Z. The page is 16 figures plus one empty one (FIG. ∅, the void: an overlay of the others' outlines, with no data of its own, so it has no section here). bot.json has one section per figure, named for what it shows, built from the values the figures were drawn with. Numbers carry the precision the page prints or its bars encode. ## Files - [bot.json](bot.json): Every figure's data as named fields (JSON, schema version 1). - [index.html](https://here.aaajiao.md/bot/): The page. Its figures are the source of bot.json. Updates: rebuilt and republished by hand (`bash scripts/bot/publish.sh`); no fixed schedule. Every number is a snapshot of `meta.generated` and expires at the next build. ## Reading contract - Only what the page shows is exported. Not included: layout (positions, label boxes), the publish receipt id in the page head, unlabelled concepts (only counted), prediction texts and ids, surprise-log summaries, cron expressions and source time zones, memory and dream contents. - Dates are YYYY-MM-DD in Berlin time unless the field says ISO. - null means the source had no value; the page prints "—" there. Nothing is filled in. - `meta.counts`: figures, capabilities, commits, cronJobs, surpriseLogEntries, expectationChecks, reviewsShown, corrections, conceptNodes, conceptEdges, dailyLogs, deepDives. ## bot.json — sections | Field | Description | |-------|-------------| | meta | {schemaVersion, url, title, generated (ISO build time), counts} | | identity | FIG. 0 · metadata (001): What the bot says it is: field / value pairs, each with a note on what the value means in this body. | | lifeline | FIG. 1 · chronograph (002): Capability emergence order from birth to the build day, and commits per month. | | anatomy | FIG. 2 · anatomy (003): The body structures around one empty centre, with up to three confidence rings. | | structures | FIG. 3 · structure cards (004): One card per body structure: what it filters for, the crack it cannot see past, how it works, and its live counts. | | helix | FIG. 4 · double helix (005): Per month, commits touching perception paths (scan, signals, research and other collectors) against commits touching maintenance paths (docs, corrections, tests, health checks, runtime setup, dependencies). | | constellation | FIG. 5 · spine constellation (006): The concept association graph laid out by force, with chords for concept pairs that are moving closer. | | breath | FIG. 6 · breath cycle (007): When the scheduled jobs fire across one week: weekday by Berlin hour. | | polygraph | FIG. 7 · polygraph (008): How surprised the signals system was: each expectation check compares what it expected with what happened (0 = as expected, 1 = fully violated). | | ledger | FIG. 8 · predictions ledger (009): The most recently reviewed predictions (at most 60) as a punch card, oldest first. | | scars | FIG. 9 · scar map + revision history (010): Every correction the bot recorded about its own behaviour, as a scar, oldest first. | | dreaming | FIG. 10 · dreaming (011): Memory consolidation: recall events, dream runs (light / deep / REM), and promotions into long-term memory. | | metabolism | FIG. 11 · metabolism (012): Activity density over the last 40 days: commits, memory files written, recall and dream events per day. | | utterance | FIG. 12 · utterance fingerprint (013): Words the last 20 daily logs use distinctively more than earlier logs. | | sediment | FIG. 13 · sediment (014): Daily logs written per month, with the deep-dive research reports of each month. | | topology | FIG. 14 · topology (015): Where the bot runs and what connects to what: two execution environments, scheduler, git, sites, channels, the world and aaajiao. | | now | FIG. 15 · now (016): The live numbers read once at page generation. The page's last cell (∅, not counted) carries no number and is not exported. | ## Figures ### identity — FIG. 0 · metadata (001) What the bot says it is: field / value pairs, each with a note on what the value means in this body. Source: Hand-written in the page; read back from it. Caveats: Self-description, not measurement. | Field | Meaning | |-------|---------| | [].field | Field name (kind, body, continuity, …) | | [].value | The value | | [].note | What the value means here | ### lifeline — FIG. 1 · chronograph (002) Capability emergence order from birth to the build day, and commits per month. Source: git history: first commit date of each capability's path; monthly commit counts up to the build day. Caveats: A date is when the path first appeared in git, not when the capability started working. Capabilities dated after the build are not drawn. | Field | Meaning | |-------|---------| | birth | First commit date (YYYY-MM-DD) | | today | Build day, Berlin (YYYY-MM-DD) | | ageDays | Days from birth to the build moment | | totalCommits | Commits from birth to the build day | | capabilities[].label | Capability (English) | | capabilities[].zh | Capability (Chinese) | | capabilities[].kind | skill / organ / flow / process / surface | | capabilities[].date | First commit date of its path | | commitsByMonth[].month | YYYY-MM | | commitsByMonth[].commits | Commits that month | ### anatomy — FIG. 2 · anatomy (003) The body structures around one empty centre, with up to three confidence rings. Source: Rings: confidence components in the current-state snapshot. Readings: counts recomputed at build time. Caveats: A missing confidence component is null and its ring is not drawn; nothing is filled in. | Field | Meaning | |-------|---------| | confidence.tier | Confidence tier (high / medium / low) | | confidence.resonance | Resonance confidence, 0-1 (2 decimals) or null | | confidence.accuracy | Prediction calibration accuracy, 0-1 or null | | confidence.snapshot | Snapshot quality score scaled to 0-1, or null | | structures[].direction | Compass slot (N, NE, …) | | structures[].kind | Structure id | | structures[].name | Name (Chinese) | | structures[].en | Name (English) | | structures[].reading | The reading printed under it | | structures[].live | true = read from live data, false = static count | ### structures — FIG. 3 · structure cards (004) One card per body structure: what it filters for, the crack it cannot see past, how it works, and its live counts. Source: Filter / fissure / description are hand-written in the page; live counts are read at build time. Caveats: Prose is opinion about the system, written by it; counts are a build-time snapshot. | Field | Meaning | |-------|---------| | [].index | Card number | | [].direction | Compass slot or ↔ | | [].name | Name (Chinese) | | [].en | Name (English) | | [].mechanism | One-line mechanism | | [].source | Where its data lives | | [].filter | What it lets through | | [].fissure | What it cannot tell | | [].description | How it works | | [].live | Live counts as printed | ### helix — FIG. 4 · double helix (005) Per month, commits touching perception paths (scan, signals, research and other collectors) against commits touching maintenance paths (docs, corrections, tests, health checks, runtime setup, dependencies). Source: git history with changed paths, up to the build day. Caveats: One commit may count toward both strands or neither. The current month is partial (partialMonth, through throughDay). The judgment loop (card 09) is a third reading drawn as rungs across the spine, not a strand: loop counts commits touching the loop's own paths, and the page prints it under the month, marked ↔, where it is above zero; each such month also has a dot on the spine, so a month with very few loop commits still shows. The loop's docs and tests also count as maintenance, so its months lift the inner strand. Once there are more than fourteen months, the page compresses the months before the latest twelve and prints counts only for the latest twelve; a compressed month too narrow for a full turn is drawn as an outline and keeps its loop rung without the dot; months[] always has every month. | Field | Meaning | |-------|---------| | status | ok, or 'git unavailable' (then months is empty) | | partialMonth | The unfinished month (YYYY-MM) | | throughDay | Last day counted | | months[].month | YYYY-MM | | months[].total | All commits that month | | months[].perception | Commits touching perception paths | | months[].maintenance | Commits touching maintenance paths | | months[].loop | Commits touching the judgment loop's own paths (rung half-length, same scale as the strands; 0 = no rung) | ### constellation — FIG. 5 · spine constellation (006) The concept association graph laid out by force, with chords for concept pairs that are moving closer. Source: The concepts graph (nodes and edges) and the converging-pairs report written by the concepts scan. Caveats: Only concepts the page labels or gives a hover are listed; the rest are anonymous dots, only counted. A pair 'moving closer' was co-mentioned in the recent window faster than either concept alone (lift); co-mention is per document, so a news outlet can move closer to whatever it reported on. | Field | Meaning | |-------|---------| | nodes | Concept count | | edges | Relation count | | maxDegree | Highest degree | | hubThreshold | Degree at which a concept counts as a hub | | hubs | Hub count | | labelled | Concepts with a printed label | | converging.status | ok / missing / unreadable | | converging.windowDays | Recent window in days (null unless ok) | | converging.minCountWindow | Minimum co-mentions in the window | | converging.minLift | Minimum lift | | converging.reported | Pairs in the report (after dropping private ones) | | converging.drawn | Pairs drawn (both ends in the graph) | | converging.pairs[].from | Concept id | | converging.pairs[].to | Concept id | | converging.pairs[].fromLabel | Label | | converging.pairs[].toLabel | Label | | converging.pairs[].countWindow | Documents co-mentioning both in the window | | converging.pairs[].countTotal | Documents co-mentioning both overall | | converging.pairs[].lift | How much faster than either alone | | concepts[].id | Concept id | | concepts[].label | Label | | concepts[].type | concept / thinker / movement / pattern / reading / other | | concepts[].degree | Number of relations | | concepts[].hub | Degree at or above hubThreshold | | concepts[].labelled | Label printed on the figure | | concepts[].movingCloserTo? | Labels it is converging with (only for chord endpoints) | | concepts[].tags? | Up to 3 tags (when not converging) | ### breath — FIG. 6 · breath cycle (007) When the scheduled jobs fire across one week: weekday by Berlin hour. Source: A cron snapshot refreshed by hand from the scheduler; each job converted from its own time zone to Berlin time in the snapshot's week. Caveats: Not live scheduler state: snapshotAt says how old it is. Disabled and one-off reminder jobs are excluded. Jobs with no firing in that week are counted in `jobs` but not drawn. | Field | Meaning | |-------|---------| | snapshotAt | When the cron snapshot was taken (ISO) | | jobs | Jobs in the snapshot | | drawn[].name | Job name | | drawn[].kind | pipeline / notify / retro / dream / maintenance | | drawn[].firings[].day | Berlin weekday (MON … SUN) | | drawn[].firings[].hour | Berlin hour | | drawn[].firings[].minute | Minute | ### polygraph — FIG. 7 · polygraph (008) How surprised the signals system was: each expectation check compares what it expected with what happened (0 = as expected, 1 = fully violated). Source: Two measurements: the surprise log (written only when a check found a violation) and the expectation checks kept in recent daily snapshots (every check, including 0). Caveats: The two eras are different methods and are never joined. Daily snapshots are rotated after about 30 days, so checkTicks start at checksFrom. A check with no verdict saw nothing it could judge: its 0 means 'could not see', not 'no surprise'. stale = the previous run's verdict carried forward. Gaps longer than 3 days are cut from the axis. | Field | Meaning | |-------|---------| | logEntries | Surprise-log entries | | logOnlyEntries | Entries before checks are retained | | checks | Retained expectation checks | | zeroChecks | Checks with a verdict and surprise 0 | | noVerdictChecks | Checks with no verdict | | staleChecks | Carried-forward checks | | violationChecks | Checks with at least one violation | | checksFrom | Date of the first retained check, or null | | axisBreaks | Gaps cut from the time axis | | log[].timestamp | When (ISO) | | log[].date | Day | | log[].surprise | Surprise 0-1 | | checkTicks[].timestamp | When (ISO) | | checkTicks[].date | Day | | checkTicks[].surprise | Surprise 0-1 | | checkTicks[].violated | Expectations violated | | checkTicks[].confirmed | Expectations confirmed | | checkTicks[].unobservable | Expectations it could not observe | | checkTicks[].verdict | Reached a verdict (violated + confirmed > 0) | | checkTicks[].stale | Inherited from the previous run | ### ledger — FIG. 8 · predictions ledger (009) The most recently reviewed predictions (at most 60) as a punch card, oldest first. Source: The prediction review log. Caveats: Only the review date and outcome are shown; prediction texts are not on this page (see /wv/ for open predictions and the scorecard). | Field | Meaning | |-------|---------| | counts.correct | Correct / hit | | counts.partial | Partial | | counts.wrong | Wrong / miss | | reviews[].reviewDate | Review date | | reviews[].outcome | correct / partial / wrong | ### scars — FIG. 9 · scar map + revision history (010) Every correction the bot recorded about its own behaviour, as a scar, oldest first. Source: The corrections ledger. Caveats: Public text only: contracts, amounts and private symbols are blanked with ▒. Unhealed = still open or deposited, or a confirmed recurrence after verification is still open. | Field | Meaning | |-------|---------| | count | Corrections | | unhealed | Unhealed corrections | | revisions[].rev | Revision id R01, R02, … (by date) | | revisions[].id | Correction id | | revisions[].date | Observed date | | revisions[].level | 1-4 | | revisions[].tier | test / guard / pattern / memory (where the fix lives) | | revisions[].status | Lifecycle status (open, deposited, verified, …) | | revisions[].unhealed | See caveats | | revisions[].confirmedRecurrences | Reviewed recurrences confirmed as this correction coming back | | revisions[].description | What went wrong and the lesson | ### dreaming — FIG. 10 · dreaming (011) Memory consolidation: recall events, dream runs (light / deep / REM), and promotions into long-term memory. Source: The memory engine's event journal for this workspace. Caveats: Three kinds of event counted separately; they are not one funnel. A dream run belongs to the Berlin night it completed in. The journal is capped upstream and drops its oldest events: every count here covers only the journalEvents it still holds, starting at nights.from, which moves forward over time. They are not running totals. The night at nights.from may be cut by the window: a phase missing there may have been dropped rather than skipped. | Field | Meaning | |-------|---------| | journalEvents | Events of all types currently held in the journal | | recallEvents | Recall events | | dreamRuns | Completed dream runs | | promotions | Promotions applied | | nights.from | Night of the oldest event still in the journal | | nights.to | Last night (build day or later event) | | nights.count | Nights in the span | | phaseNights.light | Nights with a light phase | | phaseNights.deep | Nights with a deep phase | | phaseNights.rem | Nights with a REM phase | ### metabolism — FIG. 11 · metabolism (012) Activity density over the last 40 days: commits, memory files written, recall and dream events per day. Source: git history, dated memory files, the memory event journal. Caveats: An activity proxy: it does not measure CPU, disk, API use or resource health. 41 Berlin days ending on the build day. | Field | Meaning | |-------|---------| | days[].date | Berlin day | | days[].commits | Commits | | days[].memoryFiles | Memory files dated that day | | days[].dreamEvents | Recall + dream events; null before the journal's oldest event | ### utterance — FIG. 12 · utterance fingerprint (013) Words the last 20 daily logs use distinctively more than earlier logs. Source: Daily memory logs: weighted log-odds with an informative prior (Monroe et al. 2008); a term must appear in at least 4 logs. Caveats: Lines about holdings or trading are removed at the source; ticker-like all-caps tokens and security names are dropped. Chinese terms are two-character words, sometimes widened to the longer phrase they live in. | Field | Meaning | |-------|---------| | recentLogs | Logs in the recent window | | baselineLogs | Earlier logs used as baseline | | zh[].term | Chinese term | | zh[].z | Log-odds z score (1 decimal) | | zh[].uses | Uses in the recent logs | | en[].term | English term | | en[].z | Log-odds z score (1 decimal) | | en[].uses | Uses in the recent logs | ### sediment — FIG. 13 · sediment (014) Daily logs written per month, with the deep-dive research reports of each month. Source: Dated memory files and dated research directories. Caveats: A month with deep dives but no daily logs still appears, with 0 logs. | Field | Meaning | |-------|---------| | dailyLogs | All daily logs | | deepDives | All deep dives | | months[].month | YYYY-MM | | months[].dailyLogs | Daily logs that month | | months[].deepDives | Deep dives that month | ### topology — FIG. 14 · topology (015) Where the bot runs and what connects to what: two execution environments, scheduler, git, sites, channels, the world and aaajiao. Source: Hand-written nodes and edges; the cron / sites / scripts counts are recounted at build time. Caveats: Conceptual wiring, not a network map. No addresses or account ids. | Field | Meaning | |-------|---------| | counts.cronJobs | Jobs in the cron snapshot | | counts.sites | here.now sites | | counts.scripts | Script files in the workspace | | nodes[].id | Node id | | nodes[].label | Label | | nodes[].sub | Sub-label | | nodes[].kind | core / env / sched / vcs / out / in / user | | edges[].from | Node id | | edges[].to | Node id | | edges[].kind | control / flow / in / out / sched | ### now — FIG. 15 · now (016) The live numbers read once at page generation. The page's last cell (∅, not counted) carries no number and is not exported. Source: The worldview snapshot, current-state, concepts, scan index, research, docs-health history, corrections, cron snapshot, memory. Caveats: Every republish overwrites them; they expire. null = the source had no value (the page prints —). | Field | Meaning | |-------|---------| | regime.name | Current regime | | regime.description | Regime description as printed (cut at 60 characters) | | confidence.composite | Composite confidence | | confidence.tier | Tier | | confidence.resonance | Resonance | | confidence.accuracy | Accuracy | | confidence.snapshot | Snapshot score 0-1 | | anomalies.total | Live anomalies | | anomalies.critical | Critical | | anomalies.high | High | | predictionHitRatePct | Prediction hit rate, % | | predictionsReviewed | Predictions reviewed | | calibrationPct | Prediction calibration accuracy, % | | calibrationCases | Cases behind it | | calibrationTemperature | Calibration temperature | | concepts.nodes | Concepts | | concepts.edges | Relations | | scan.tracked | Scan topics tracked | | scan.states | Lifecycle states | | scan.promotePending | Topics suggesting a deep dive | | research.threads | Deep-dive reports | | research.briefDate | Date of the research brief | | immune.issues | Issues in the last full health patrol | | immune.warnings | Warnings | | immune.modules | Check modules | | immune.lastFullPatrol | Date of that patrol | | corrections.open | Open corrections | | corrections.selfRegressionPending | Self-regression candidates awaiting review | | predictions.all | Open predictions | | predictions.manual | Manual | | predictions.synthesis | Synthesis | | predictions.auto | Auto | | surprise.value | Latest surprise 0-1 | | surprise.note | Its reading | | cronJobs.total | Scheduled jobs | | cronJobs.pipeline | Pipelines | | cronJobs.retro | Retros | | cronJobs.maintenance | Maintenance | | dailyLogs | Daily logs written |