Corteza supports configurable business applications with namespaces, modules, fields, relations, and workflows. A firm that has built its own operating model on Corteza should retain that structure. Selected exports can support a focused Uranus review without attempting to rebuild the entire configured application.

Begin with the instance administrator: establish the deployed version, module schema, and role-limited record scope. Preserve both raw relation identifiers and readable labels where the version supports them. The documented export behavior has changed across releases, so a layout that worked in one installation should not be assumed to match another.

For a fictional VC review, import the permitted company and metric context, attach a supporting document, and assign the unresolved question. Uranus tracks owner, requested evidence, and reviewed resolution. A later integration would also need to handle Corteza’s documented error envelopes and update semantics carefully; omitted fields in a broad record update can matter. This release performs no Corteza writes and includes a guide with generic mapping rather than native sync. Corteza’s Apache license permits reuse under its conditions, but this build uses original domain logic and preserves the distinction between inspiration, dependencies, and copied code.

A first import you can review

  • Ask the instance administrator for the deployed version, namespace/module schema and role-limited export.
  • Export needed record fields and include raw relation identifiers alongside labels where the deployed version supports it.
  • Use documented Compose API for selected records/attachments; preserve namespace/module IDs and multi-value fields.

What Uranus adds today

Review the mapping, units, currency, and reporting month before committing. New metrics remain candidates until a workspace owner reviews them. Preserve originals and source identifiers, keep the requested next evidence visible, and attach a reviewed resolution when the work is complete. Export canonical records and version history when you need to move the work again.

This is a proposed workflow based on public documentation, not a paid-account benchmark or a demonstrated performance improvement. Verify the actual entitlement, export schema, and effective permissions with the firm’s administrator. Native formats require customer fixtures before claiming automatic compatibility.