Chronos Coming soon

Standalone / Local / Evidence-led

A way back.
Not a shortcut.

Revit backward compatibility deserves more than a changed version marker. Chronos is a standalone research tool exploring how newer families and projects might reach older Revit environments without hiding what is lost.

No native .rfa or .rvt down-conversion exists today. The current prototype only inspects local evidence and compares container directory structure. Desktop UI and all translation routes are concepts or research.

Concept preview: two synthetic evidence panels connect through a Chronos evidence gate. Inspection is separate from unverified target research.
Concept preview / Original illustration, not a working converter screenshot.
Implemented inspectionRead-only evidence CLI

CFB container and journal inspection; structural directory comparison.

Concept previewDesktop evidence workspace

Illustrative panels below. No files can be selected or processed on this site.

Not availableTranslation or verified output

No conversion, replay, source-version verification or Revit-host validation.

Concept preview / Synthetic evidence only

See the unknowns before the next step.

The concept workspace keeps inspection, comparison and compatibility decisions separate. These panels explain the intended experience; they do not run the prototype.

CHRONOS / Evidence workspaceConcept preview

Before evidence

Explicit file copy

  • Validate CFB allocation
  • Retain a local fingerprint
  • Record storage-qualified paths

After evidence

Compare, not interpret

  • Validate the second copy
  • Compare directory metadata
  • Leave payload meaning unknown
Explore the paired-file comparison concept

Implemented CLI scope: structural directory comparison only. The illustrative rows below are not measured output.

Synthetic comparison vocabulary
EvidenceWhat it can establishWhat it cannot establish
Storage-qualified entryWhich directory path differsWhich Revit feature changed
Stream metadataA structural metadata differenceGeometry or parameter semantics
File fingerprintWhich selected copy was inspectedIts verified source Revit release
Explore the blocked compatibility preflight concept

Translation blocked: source release unverified. A future preflight must establish source identity through supported host APIs, check an explicit target adapter and explain unsupported features. None of those checks exists yet.

Choosing a requested release would never create support by itself. There is deliberately no enabled conversion control.

Read the C2 exit gate

Local-first intent: selected copies in, local reports out. This static website never receives model files.

Product roadmap / Engineering sequence, not a schedule

Every feature has an evidence gate.

Implemented inspection is a starting point, not proof of conversion. Planned features remain blocked until their dependencies and independent validation are established.

C0 / EvidenceImplemented inspection

Read the container. Keep the evidence.

Inspect an explicitly selected local file copy and optional journal evidence. Keep decoded journal text, fingerprints and explicit blockers in a local report.

Gate: Bounded read-only CFB allocation validation and host-free synthetic tests. The inspection CLI exists; its desktop interface is a concept.

C1 / ComparisonImplemented inspection

Separate structural change from meaning.

Compare validated directory metadata with storage-qualified paths and source fingerprints. Do not decode payloads or infer semantic changes from a directory difference.

Gate: A consented synthetic version-paired corpus, one controlled edit per save. Structural comparison CLI implemented; corpus and UI pending.

C2 / PreflightPlanned

Make compatibility an explicit decision.

A verified source-version badge, requested target and feature coverage matrix should explain blockers before any translation begins. Unknown source identity must stop translation.

Gate: Supported source-host metadata, validated release/document pairs and explicit target adapters. No source-version verification or target adapter exists.

C3 / ReconstructionResearch

Preserve design intent, not just shape.

Investigate a versioned semantic graph with explicit feature mappings. References, units, formulas, hosts and constraints need their own representation and lowering rules.

Gate: Verified extraction, reference invariants and proven target features; rights and terms review before proprietary payload research. No decoder, semantic graph or writer exists.

C4 / ProvenanceResearch

Keep lineage and dependencies visible.

Review journal participants, ordering, central lineage and unresolved dependencies. A journal or delta stream is evidence, not an automatically replayable recipe.

Gate: Complete synthetic baselines and verified event semantics, with separate family and workshared-project routes. Journal classification exists; reconstruction and replay are unavailable.

C5 / VerificationPlanned

A result needs a validation ledger.

Inspect load, geometry, text, parameters, formulas, constraints, family regeneration, dependencies and worksharing where applicable. Review save/reopen and explicit rollback outcomes.

Gate: Separate disposable source/target-host checks and safe destinations that never overwrite sources. No Revit-host checks have been completed.

C6 / BatchPlanned

Scale only a proven subset.

A future queue should isolate failures, explain filename collisions and support cancellation. Completed, failed and unattempted files must remain distinct in per-file reports.

Gate: A validated conversion subset first; then isolated operations and tested cancellation. No batch conversion exists.

Concept preview / Route decisions

Several routes. The same burden of proof.

Concept preview: local evidence branches into binary-schema research, journal-lineage research and source-host API research. All require a verified semantic graph, explicit target mapping and independent target-host validation. None is an available conversion route.
Concept preview. Arrows express research dependencies, not an implemented conversion pipeline.

Binary translation / research

Public CFB metadata is not a Revit serialization schema or memory layout. No version-marker patching and no fabricated older-format files. A writer needs established versioned schemas, reference invariants and independent validation.

Journal reconstruction / research

Retain evidence until baseline, lineage and event dependencies are understood. Do not strip apparent UI events or assume journals and .dat streams can be replayed. Standalone families need a separate route.

Host reconstruction / research

Investigate supported public source APIs as a parallel extraction route. Lower only proven features into an explicit target adapter, then validate in the actual target host. No adapters are available.

Research intent / Not verified coverage

The release number is not the evidence.

Revit 2025+ source releases and Revit 2018-2024 targets are research intent only. Neither range is supported-version coverage. No source/target combination has passed Revit-host validation.

Families (.rfa) and projects (.rvt) have different dependencies and need separate validation. Workshared projects also require central lineage and history; a standalone family does not follow the same route.

Intended investigation

Source research
Revit 2025+
Requested targets
Revit 2018-2024
Verified conversions
None
Availability
Coming soon / no launch date announced

Not a promise of lossless conversion.

Clear answers, before expectations.

Can I convert or download a model here?

No. There is no converter, application download, upload form or hosted processing on this page. The prototype is read-only inspection tooling; the desktop workspace is a concept.

Is Chronos part of the Codex add-in?

No. Chronos is a standalone Revit backward-compatibility research product, separate from the Codex CAD-detail add-in. Their purposes, implementation and validation requirements are distinct.

Read about Codex separately
How would my files be handled?

Prototype processing stays local, on explicitly selected copies. Research uses wholly synthetic, permissioned samples, never client-folder scanning. A future delivery route must use a safe destination and never overwrite source files. This page sets no cookies and stores no waitlist or model data.

When will it launch, and what will it cost?

No launch date, pricing or download availability has been announced. This is a static coming-soon presentation, not an application release, checkout or entitlement service.

Chronos prototype: all rights reserved. Copyright-owner attribution is pending confirmation. Third-party rights remain independent. No Autodesk endorsement is implied.

Return to the concept workspace · Explore current Xenon product pages