# Chronologue canon

The "Chonologue" refers to the telescope itself. The Chronologue telescope uses wormhole technology to view astronomical events through time. It is inspired by the James Webb Telescope in our present day.

The organization that runs the Chronologue telescope is **OCTAVIA**, which stands for Organized Consortium To Activate Visual Information in Astronomy. It is inspired by NASA in our present day.

```{note}
 In written documentation, it should be referred to as “OCTAVIA’s Chronologue telescope” the first time you use it in a document or sentence. If you’ve used it once already, you can shorten it to “OCTAVIA’s Chronologue.” This is similar to how NASA refers to the James Webb telescope.
```

KronoPy is an open source community of Python developers who build libraries to extract information from the Chronologue API and process and analyze data.

```{note}
For more information on KronoPy, see the {doc}`KronoPy/kp_index`.
```

Zaius Inc. creates commercial products based on the Chronologue API. Their main product is the Chronologue Relay, which is a home console that can connect the Chronologue API to your home Virtual Reality (VR) headset and view astronomical events in time.

```{note}
For more information on Zaius Inc, see the {doc}`Zaius_Inc./z_index`.
```

By contrast, the “Chronologue project” is the off-stage (in real life) project that creates the documentation and tool for The Good Docs Project.


## How does the Chronologue work?

The Chronologue creates wormholes to observe the universe at different locations and times. The Chronologue can receive data from across the electromagnetic spectrum.

To observe an event, the Chronologue creates a microscopic wormhole linking two different places, in geostationary orbit around a source of gravitation. This gravitation source is the anchor for the wormhole opening, and while this gravitational source exists \- so does the wormhole opening. The Chronologue can use its own wormhole endpoint to observe the linked endpoint at any time in which that endpoint exists. This allows the Chronologue to observe events at any time during the lifespan of the linked gravitational presence.

Additionally, the Chronologue can create additional wormholes from its observation points. Any wormhole created by the Chronologue can be used as the origin point to create another wormhole. This allows the Chronologue to observe almost anything in both time and space.

This may seem dangerous; however, the Chronologue has no need to actually perform this function. The Chronologue needs only open a single wormhole, one to observe itself in the future. By observing itself in the future, the Chronologue can obtain data from itself, allowing it to bypass needing to create wormholes to observe events.

This paradox allows the Chronologue to limit energy usage, and instantly provide data on observed events without needing to observe the event.

OCTAVIA’s chronologists are still developing theories on how this is possible, but are limited by laws on preventing the intentional creation of paradoxes.

```{note}
The paradox described above was the event that required the creation of laws preventing the creation of paradoxes.
```

### How is Chronologue data stored?

Chronologue data is stored in massive databases. However, data is also streamed continuously through optical data transmission to allow observation by the Chronologue in the past.

### Paradox prevention

The Chronologue routinely checks its own future database to retrieve information. Some information may be restricted until specific conditions are met. This is to prevent paradoxes from occurring.

For example, information about future human existence is restricted. However, additional random information is also restricted as specific restricted information can also be informative enough to produce a paradox.

```{note}
This allows TGDP contributors to not address specific questions or provide specific information under the justification of paradox prevention.
```

### OCTAVIA's Chronologue API

The Chronologue has an exposed API for interaction by third parties. Any information the Chronolouge has not restricted is available through the API, but there are rate limitations for unauthorized parties. Authorisation is granted to open-source projects, researchers, and paid customers.

## On-stage users

### OCTAVIA users

OCTAVIA users would use the exposed Chronologue API. OCTAVIA has no other products, so OCTAVIA documentation would largely be focused around using the Chronologue API and reporting issues. Communities would likely emerge around the significant users of the Chronologue like KronoPy and Zaius Inc., rather than OCTAVIA itself.

### KronoPy users

KronoPy users would be those that have a reason to use the KronoPy project. The project itself is used for processing data from the Chronologue, and would consist of libraries and applications that transform or manipulate data. KronoPy documentation would likely emulate the same documentation as the real-world equivalent \- [AstroPy](https://docs.astropy.org/en/stable/). This includes usage and contribution to the project. 

### Zaius Inc. users

Zaius Inc. users would extend from enthusiasts to researchers. As Zaius Inc. is, in canon, the best way to visualize and interact with the data from the Chronologue, Zaius Inc. would have documentation focused on its products, and contributing to the open-source codebase.


## Prior art and references

The Chronologue canon task force used these materials as inspiration for what we knew about the Chronologue world up to this point. Special thanks to Carrie MacFarlane and Ogunkelu Shola for assembling these resources:

* Original Canon proposal: [Chronologue Canon - The Good Docs Project](https://docs.google.com/document/d/1RYIihvwLYL7YN2sR8oKFpOhNdb-B3_Bl1AcvK050cEE)  
* Chronologue Working Group page on The Good Docs site [https://thegooddocsproject.dev/working-group/chronologue/](https://thegooddocsproject.dev/working-group/chronologue/)   
* Old Chronologue repo wiki [https://github.com/thegooddocsproject/chronologue/wiki/About-Chronologue](https://github.com/thegooddocsproject/chronologue/wiki/About-Chronologue)   
* Old Chronologue documentation proposal [https://github.com/thegooddocsproject/chronologue/wiki/Chronologue-documentation](https://github.com/thegooddocsproject/chronologue/wiki/Chronologue-documentation)