utopia

Two weeks in which a document's own dates began to govern what is true when: extraction reads time as it goes, a statement is attested by the date its section speaks from, and a deleted document stops attesting. The ontology is now proposed from the open graph and judged by the questions it answers. Word, Excel, PowerPoint and PDF files are read as they are laid out. This is also the first tag published for linux/arm64 as well as linux/amd64.

Time is read as the document speaks

• Extraction reads time as it goes (0064, #989). Each chunk reports the dates its passage states, and a time word is measured from the date of its own section (#991). A statement is attested by that date, and one with no time holds at every moment (#995). A document that states no date is not asked for one (#998).
• The uniqueness timeline orders a row without a start by its attestation (#1054). Each piece of evidence records when its passage speaks, so a deleted document's date no longer attests (#1059). A row a rule implies is attested by the statements it read (#1012).
• A binding to a state property says which end a single date marks, and a state row with equal ends is never written (#975). An end the timeline derived cites the fact that closed the row, and a corrected date says which end a person changed (#986, #976). A corrected fact keeps the statements it was computed from (#967, #972).
• Time mentions resolve whatever order the model lists them in (#1087). A pushed statement's complete date or zoned timestamp is resolved in code, with no chat model (#1090). A quote and its time words are found across a line break (#1081), a deck's cover date attests every slide (#1082), and an upload's date is read from its filename before its body (#979).

The ontology is proposed from the open graph and judged by its questions

• Competency questions are rows of a base. An agent proposes classes and properties from the signatures and kind words nothing binds, each with a definition and the statements behind it; adopting one writes the element and re-decides those shapes (0061, #945, #947).
• The agent remembers what it has seen, and "already in the ontology" becomes a proposal a person adopts as a binding (#950). It proposes questions for a base that has none, and the ontology is measured by two numbers (#955, #962). Its glossary is trimmed per batch the way alignment picks candidates (#963, #965).
• The editor refreshes the ontology's vectors before alignment runs (#956). A kind-word decision records the inputs it considered (#932). An empty ontology says what the documents still need (#1083). A SHACL shape gives a property the domain and range it does not declare (#1001), and an xsd:hexBinary range is imported as text (#1008).

Alignment and extraction

• Every model call uses the workspace's reasoning effort, and none is a value: alignment no longer thinks on its own (#1066).
• Phrase alignment batches signatures by their candidates, casts no second vote after a first that says none, and asks no rules of a bare head word (#999). Class definitions are written once per batch of kind words (#1004). Phrase alignment waits for the last kind-word round (#926).
• An extraction reply that is not valid JSON is read item by item, and a slot of the wrong type costs only that slot (#1003, #1011). The usage log says which call it was (#996). The extraction loop is split into call and apply halves, ahead of concurrent chunks (#980).
• On large bases: the signature queries make one pass instead of one scan per group (#1108), and signatures are not embedded while no property has a vector (#1107). Both come from a deployment with 36,000 open statements.

Documents are read as they are laid out

• Word: headings are read as headings, so sections reach the chunks and each is dated by its own date (

Six days in which the typed graph became a view that keeps itself honest: alignment learned to reconcile what it writes, to shortlist what it asks about and to read a model's answer in whatever shape it comes; an errata agent now needs two votes and a structural reason before it retracts anything; a name meets its entity through a vector as well as a string; and a source can push statements straight into the open contract.

Alignment writes a view, and the view reconciles itself

• A phrase decision records the inputs it considered, so a binding is stale when its basis changed, not when a clock says so (0053, #878). A human decision commits with its own recomputation job and answers 202 (0051, #876).
• Materialization reconciles the rows it writes along their uniqueness timelines, as the write path always did, so a later observation of a functional attribute closes the earlier one without a manual reconcile; a document version keeps the date it was pushed with, so a same-identity update no longer makes two values look simultaneous (#911, from the #875 replay in #898).
• A shape of statement can imply a fact of another property, read once per phrase and cached (#882); a business rule may join two entities and conclude a relation (0047, #861); a rule's definition has a history, and a conclusion names the version it was drawn under (0060, #913).
• The aligner reads the kind-word and phrase replies in the shapes models actually write, and asks again a bounded number of times, so a whole base no longer stays untyped in silence (#894, #895). When the structure fits more than ten properties it shows the ten nearest by the ontology's own vectors, describes the candidates once per batch, accepts a label where a key was asked for, and asks for rules only about bound signatures (#906).
• Each task thinks as hard as it needs: chat_reasoning_effort in the workspace settings rides on every chat call, extraction and errata run at minimal, alignment and rule proposals at low, all measured on the typed-graph bench (#906, migration 0075).

An errata agent, on two votes and a flag

An agent reviews each document's typed facts through the gate, structure first (0044 decision 7, #885). The first measured runs showed it retracting mostly what the document did say, so a retraction or revision now needs a structural flag and a second vote asked alone with the document; an unflagged fact is never retracted by the agent alone. Additions opened the other way: a name the document contains becomes an entity, and a document with no typed facts is reviewed once with an empty list (#906). On 100 documents: 34 wrong retractions to zero, recall 9.3% to 18.4%.

A name meets its entity

Recall proposes a pair by name vector, so a short form or a name in another script meets its entity through a question rather than a silent second entity (0041 cut 2, #877, migration 0080). A pair proposed by similarity rather than by the same string is never merged on the batch verdict alone: it takes the tool-using second look, or goes to a person when that look cannot run (#889). Review paging looks the two entities up before their same-name peers (#888).

A source may push statements

A Statements source accepts the open extraction contract over HTTP with its own push token: what a client sends is what the graph reads, no model in between, and it reaches the typed layer the same way a document does, through alignment. Same identity is an update, deleted is a tombstone, a key outside the contract or a subject not listed is refused at the door ([0054](do

Two weeks in which extraction stopped writing into a schema and started writing what documents say, and alignment learned to turn that back into typed facts. The ledger, the interface and the reading of files all moved with it.

A document is read in its own words

Extraction writes an open graph — the subject, the relation phrase as written, the object, the quote it came from — and nothing is bent to fit a class on the way in (0044, #710, #731, #736).

• The quote is the first thing a statement carries, so the model copies the sentence before it writes from it (#748)
• A statement reads on its own, and a thing is named by a proper name or a term that means the same in any document (#743)
• A statement says its mood: a plan, a forecast and a requirement are not facts about the world, and never become typed facts (#745, #746)
• A table keeps its headings, its sections and its caption, in HTML, in Word, in a spreadsheet and in a CSV (#744, #750)
• A memory waits in its own words rather than being written straight into the graph (#735)

The ontology is a view over that, not a gate in front of it

• A kind word binds to a class and a phrase binds to a property, each by two votes with the candidates reversed, and a person's decision is never overwritten (#741, #751)
• A bound statement becomes a typed fact through the same gate as any other fact, with its sources recorded; several statements about one triple make one row, not one each (#752, #753)
• What the aligner could not decide has a queue, beside the other review queues (#754)
• Editing a class or property definition reconsiders the negative bindings it may now fit, not only the new ones (#775, thanks @Maya-Kid)
• The ontology table can create classes and properties, not only edit them (#756, thanks @siu91)

Time

• A document is dated from its own text, every time mention is interpreted by the model and computed by code, and upload time is never a document's date (0045, #724, #740)
• A timeline closes on how a start was got, not on a number. The resolution grade travels from the mention to the statement to the typed row; a successor whose start could not be anchored closes nothing and opens no conflict, and AUTO_CLOSE_MIN_CONFIDENCE is gone from the engine (#762)

A file is read by something that says how it read it

• A chunk carries its origin — stated, OCR'd, transcribed, described — the model that produced it, and an anchor back into the original bytes (#719, #722)
• Scans and images go to a layout service; a recording is read with its speakers, and an unlabelled transcript degrades rather than lying (#720, #721)
• A PDF whose text layer uses a CJK CMap no longer panics the reader (#761, thanks @Floating-Y)
• A WebDAV file whose name contains an XML entity is no longer silently skipped (#765, thanks @Maya-Kid)

What a call to the endpoint survives

• 408, 502, 503, 504 and a request that never sent are transient and retried; 500 is not, and neither is a read timeout (#757)
• Extraction streams, so the timeout measures silence rather than thinking. A stream that stops mid-answer is a failure, not a short answer (#757), and the two live-stream paths now check the same thing (#785, thanks @Maya-Kid)
• A multi-byte character split across two network chunks survives (#764, thanks @Maya-Kid)
• The token ceiling is ours rather than the endpoint's default, and a reply cut at it says so in the drop table (#786, thanks @basil-k-aji-dev)
• Embedding responses that carry an index are paired by it, not by arrival order (#784, thanks @Maya-Kid)
• A passage that could not be extracted is a row in the drop table, not silence (#757)

Measured, and left alone

Capping the model's reasoning halves the thinking and costs a sixth of a filing's table figures, 885 statements against 729, and nearly double the

Time

• Every graph read now rewinds the second clock. as_of travels beside at all the way to the API, so the graph, its neighbourhoods and an entity's panel can be asked what we believed on a date, not only what was true on one (#317)
• A wrong extracted date can be corrected without deleting the document. The edit goes through the ledger — the old reading stays, with the correction pointing back at it (#311)

The ledger can leave

• A base exports as RDF, in Turtle or JSON-LD: GET /api/v1/kbs/{id}/export. Facts carry both clocks as reified statements, evidence rides as PROV-O lineage back to the document and the sentence, and imported classes keep the IRIs they arrived with (#320)

Ontology

• The ontology can be seen as a schema, not only edited as forms — classes as nodes, inheritance, disjointness and object properties as edges (#281, thanks @kalyp-angel)
• A deployment's first base starts with a vocabulary instead of an empty one (#325, #292)
• A class imported without a readable IRI takes its key from its label (#328)
• Type resolution runs itself after extraction, and applies only what stays inside the subtree (#297)

Who is who

• Two people with one name in a single document keep their identities (#296)
• A namesake tie now goes to review instead of being decided by the order rows came back from the database (#329, thanks @ousamabenyounes)
• The review card stops presenting a namesake pair as 100% context similarity (#310, thanks @Floating-Y)
• Disambiguating suffixes follow the ontology's own predicates rather than a four-word list, so a schema.org base stops showing two identical "John Smith · Person" (#319)
• The entity-name guard reads structure instead of a hand-written verb list (#285)

Agents and data

• An agent can record over MCP. remember is exposed to a write-scoped token held by an editor, and what it records waits in Review before entering the graph; the card names which agent said it (#318)
• MySQL-compatible warehouses can be mounted — one driver reaches TiDB, OceanBase, Doris and StarRocks (#315, #323)
• A data source is usable the moment it is registered (#294)
• Trino now has a test against a real cluster (#327)

Security

• Credentials are sealed before they reach the database (#284)
• The push key is compared in constant time (#301)
• Purging a deleted document removes its content for good (#283)

Also

Empty pages say which step comes next (#321) · the class form has room to breathe (#288) · search boxes stand at one height (#312) · one embedding refresh per base at a time (#295) · the in-app docs explain agents over MCP (#293) · the README says what ships (#291) · the benchmark gets an answer ke