04 / Living documentation

Connected documentation.
Versions that preserve the review.

Relate documents to project sources, prepare reviews and preserve baselines. Distinguish current information from content fixed in a version.

FUNCTIONAL SCOPE

What you can manage with Orkenty.

Project sources

Gather authorised requirement, work or test information according to the document source. Filters place it within the scope being reviewed.

Baselines

Capture a content version as a reference. Sources can evolve without rewriting what was fixed in that baseline.

Review and approval

Manage versions through document workflows. Preserved content and state distinguish document preparation from approval.

Formal exports

Download baseline PDF and Word files from their persisted snapshot. Template and visual identity options depend on the installed version.

Read current information within scope

A live document provides an organised reading of current project sources. Source type and filters determine the information included. Reading QA design is different from presenting execution outcomes.

The live view is useful during preparation and analysis because sources evolve. It must therefore be distinguished from a frozen reference: a current query does not establish what someone saw during an earlier review.

Fix a version for review

A baseline preserves captured content and references at creation time. It remains available after requirements, work or current labels change.

The document workflow organises review and approval according to configuration. Capturing a version does not approve it; exporting it does not change its state. Current permissions govern who can read and perform available actions.

Share documents with context

Formal PDF and Word exports use preserved baseline content. Supported tables, images and presentation belong to the scope of the installed version and renderer.

Own templates can customise presentation and visual identity where available. The aim is readable, consistent documents, without promising arbitrary CSS reproduction or treating a document fingerprint as a signature or certification.

A PRACTICAL JOURNEY

From setup to team review.

01

Select the source, project and scope.

02

Review the live document and its gaps.

03

Capture a baseline when a fixed reference is needed.

04

Manage review and export the corresponding version.

ILLUSTRATIVE USE CASE

Put the capability in context.

Before a requirements review, the team prepares a live document and captures a baseline. Next-iteration changes remain in current sources while the reviewed version remains available for consultation and export.

Available actions depend on installed version, enabled integrations and current permissions. Review your specific journey in a demonstration. The example is illustrative and is not a customer testimonial.

COMMON QUESTIONS

Understand the scope.

How does a live document differ from a baseline?

A live document reads current information. A baseline preserves a captured version and does not update when sources change.

Can I download PDF and Word?

Yes. Baselines have formal exports from their persisted snapshot. Available live downloads depend on the source and installed version.

Is a baseline an approval?

No. Capture preserves content; approval belongs to the workflow and requires the corresponding action and permissions.

A CONVERSATION ABOUT YOUR ENGINEERING

See Orkenty in the context
of your team.

Tell us what you need to connect. We will prepare a demonstration focused on your requirements, quality processes and delivery workflow.

01 · Review your process and priorities.
02 · Explore a functional workflow.
03 · Define the scope you need to evaluate.

Business contact:
info@orkenty.com

Privacy inquiries: jorge.bernal@hova-it.com · Hova-IT