Security

Where it runs

Cosmogenesis is available as a containerised application. A SaaS service is in beta.

For a reading you grant read access to source under your controls and revoke it your way. The deployment you choose, and where it sits, is settled with you before the reading starts.

In the deployment you run, the reading runs on infrastructure you control and the record stays there.

What leaves

A reading is made from the source you supply and produces a source-derived record. Production values and runtime behaviour stay with the systems that run them.

The reading itself uploads nothing and reports nothing back, and the engine's tests hold it to that. Every socket entry point is intercepted while the reading's diagnostics path runs and no connection is opened, and the source is censused for any module holding a network client so that none can be added undeclared.

Deployment, data-handling and architecture details are provided during enterprise diligence.

What is stored

What is stored is the record, a regenerable reading bound to a named source snapshot, interpreter version and generator version, and it is delivered to you as a file. How long a reading and the source it was read from are held, for the deployment you choose, is part of the diligence detail above.

Is a model involved

No. The reading is compiled from source, and the same source, read under the same conditions, gives the same record, byte for byte. A model can read the record, although it cannot establish one.

Standards we hold

None are claimed on this page. Cosmogenesis Systems Pty Ltd states what it holds during enterprise diligence and does not publish a standard it cannot evidence.

Continuity and exit

A reading has a written end date. On it you decide whether to continue, narrow the scope or stop. Access you granted is yours to revoke at any time, and the record already delivered names the source snapshot it was read from.