Skip to content
Contact RO

47NETWORK / ENGINEERING

A clear problem.
A useful result.

We bring software development and quality assurance together around a defined task, the systems you use and a result you can inspect.

01 / THE APPROACH

From a task to a checked result.

01

Define the outcome

Start with the people using the software, the task they need to complete and the environment where it should work.

02

Agree the scope

Clarify the deliverables, access and acceptance checks before implementation. Keep the work tied to the result you need.

03

Build, test and refine

For a repair, reproduce the failure, make a focused change and retest it against the original problem.

04

Make the handover useful

Review setup information, tested behaviour, known limitations and the agreed maintenance path.

02 / A CONCRETE EXAMPLE

Keep the source close to the finding.

This saved Pylotheke report uses the fictional Harbor Notes project. A comment changed outside a cited passage: the file changed, but the text at the citation’s original position did not.

Harbor Notes report: whole file CHANGED; original citation bytes UNCHANGED; change outside the cited span.
A real Pylotheke report generated from an invented example. This is a saved report image. A reviewer still decides what the comparison means for the finding. Open report image at original size Read this example in text

Keep the correction with the finding

The walkthrough starts with an intentionally mistaken finding and records its correction. Both versions remain available to inspect alongside the selected source.

Separate comparison from interpretation

The comparison checks citations at their original positions. It does not relocate a moved passage or decide whether a finding is still valid.

Pylotheke and Stemmapyle remain in development and are not available for public use or download. The example explains the local review workflow.

03 / START WITH A DEFINED PIECE OF WORK

Choose a starting point.

Investigate a problem, adapt one component or explore a private prototype. Each package sets out the deliverables and boundaries of that work.

Studio diagnosis

One named component and environment, one defined problem; no production change.

€150

View package details

Fitted software capability

One small component or configuration adaptation for one agreed environment.

from €450

View package details

Bounded private prototype

One private journey with up to three views and a scoped data adapter.

from €1,200

View package details

Business prices in EUR, excluding applicable VAT. These are prices for the stated scope; additional work is quoted separately. Purchases are not open yet.

Before we begin

What should I send?

A short description of the task, the current behaviour and the result you need. Include the relevant environment and constraints; keep credentials and confidential files out of the initial enquiry.

Does a diagnosis include the repair?

The diagnosis package investigates one defined problem and proposes a remedy. Implementation is a separate, scoped piece of work.

What happens after the handover?

Basic guidance, defect reports and correcting our in-scope delivery defects are included. Care adds optional advice and improvements; it is not a requirement for reporting a defect.

Tell us what needs to work.

Start with the task and the outcome. We can discuss the scope, price and timing before any paid agreement.