# What are space and time in GilbVeda \(changing systems\)?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

GilbPlatform keeps each fact with when it was true and when it was written, and can keep where things are, so changes can be followed.

## Deeper

GilbPlatform calls its store "the space-time of changing systems". A system is any useful part of the world that we choose to describe, real or not, such as a garden, a machine or a project; its facts change over time. A fact is one named value on a record, such as a title or a weight, and a record is one piece of data with its own address, such as a person, a place, a thing or a note. GilbVeda, the shared list of terms, gives every fact its name; GilbPlatform keeps the facts in time and in space.

Time comes twice. World time is when a fact was true in the world, from a start to an end. System time is when GilbPlatform wrote the fact down, and when it was later replaced. So "the hive weighed 40 kg on 1 May" and "we wrote that down on 3 May" are kept apart.

GilbPlatform never writes over a fact: a change closes the old fact and adds the new one. So GilbPlatform keeps every earlier version of a record, with when each fact, one value in one field, was written and who wrote it. A delete ends a record and does not erase it; an ended record can be brought back. Programs can read every fact a record has had, and the record as it stood at an earlier moment of system time; reading it as it stood at an earlier moment of world time is not offered yet. GilbApp shows no earlier versions of a record; [the answer on seeing a record as it was before](http://support.gilb.com/help/how-do-i-see-a-record-as-it-was-before-its-history) says what it shows. In "Ontology", a GilbVeda term's "CHANGE HISTORY" shows who changed it, when and what.

Space is where a thing is. A record can hold its place as a point, a line or an area on the Earth, and programs can find the records within a distance of a point or inside an area, among the records they may read. A thing's position can also be given from another thing, such as a sensor's place measured from a corner of its room, and GilbPlatform works out where it is through them, reading only what the asker may read. Any signed-in person can also record, in a vault \(the place where a person or a group keeps their records\) they may write to, where someone lives or is; the record says who said it.

Programs can turn words for a time into an exact time, for a time zone the program names.

All of this is done by programs, through GilbPlatform's interface for developers; [the developer guide](http://support.gilb.com/help/how-do-i-get-started-with-the-developer-guide) explains it. GilbApp shows a record's last change and, on a person's card, addresses and a time zone; [the answer on adding a person's addresses and time zone](http://support.gilb.com/help/how-do-i-add-a-persons-addresses-and-time-zone) shows those.

Source: Standards \(2026-11-11\): Reference\_Code\_gilb-architecture.BitemporalDatomModel \("Every fact is an append-only datom carrying transaction + valid time; nothing is mutated or deleted, only superseded — \\"the space-time of changing systems\\"."\), .DataStore \("a bitemporal append-only datom log"\); Dev.Guide.Overview.Records \("A record is one thing in a vault ... facts \(named values\)"\), .History \("The platform never overwrites a fact. A change closes the old fact and adds a new one. A delete ends a record; it does not erase it. An ended record can be brought back"\), .Vocabulary. GilbVeda \(public read / local copy 2026-11-10/11\): t:System \(Approved: "A system is any useful subset of the universe that we choose to specify. It can be conceptual or real."\), t:EventOccurrenceTime \("WHEN AN EVENT HAPPENED IN THE WORLD ... Three clocks"\), t:GeometryLiteral \("THE METRIC SHAPE OF A THING ... POINT ... LINESTRING ... POLYGON"\), t:FrameParent \("X's position ... is EXPRESSED IN F's coordinate frame ... IT IS NOT CONTAINMENT"\). GilbPlatform 498d29a0dec9a15d167f4b6b5d731382a6bcede0 \(https://id.gilb.com/version read 2026-11-11, dirty false\); every platform file cited is byte-identical to 4d008a55 except docs/BASE-DEVELOPER-GUIDE.md, whose changes touch none of the parts cited; code read at 498d29a0: docs/BASE-DEVELOPER-GUIDE.md §7.1 \(lines 7222-7240 at 498d29a0: valid\_from/valid\_to world-time, tx\_from/tx\_to system-time\), line 7638 \("?as\_of is transaction-time only today \(valid-time as-of is deferred\)"\), the history route \(GET /base/e/:id/history\), line 8163 \(GET /base/spatial op dwithin\|within\|intersects\|distance\), §"Base time" line 8826 \(POST /base/time/resolve: words or an expression to a Zulu span; "the caller passes the zone"\); src/routes/spatial.ts:1-20 \(reader-filtered, anon empty\); src/routes/geo-compose.ts:1-25 \(frame walk, every hop read-authorised\); src/routes/geo-place-claims.ts:20-50 \(any authenticated principal authors a claim about anyone, written only where they may write, attributed to the author\). GilbApp ebd9415e7a90de8c289eaa7bb02f40c8ee80cf79 \(https://gilb.com/app/version.json read 2026-11-11, dirty false\); every GilbApp file cited is byte-identical to af0f04ee \(between af0f04ee and ebd9415e, the cited files: empty\), so line numbers are read from the unpack \(no checkout\) \(no earlier versions; "CHANGE HISTORY" in Ontology, OntologyHistoryPanel.tsx:73-74\); The example \(the hive\) is the author's, made up.
