On this page

Flow Engineering Change Impact: A Requirements-to-Evidence Evaluation

Can a reviewer follow a change through to applicable evidence?

Evaluate Flow Engineering change impact by following the accepted requirement, proposed change, affected records, review disposition and evidence configuration. Flow Engineering documents a systems graph, impact checks, agents, branches and reviews. Arc connects requirements and architecture with controlled proposals and configuration-linked verification. Use the same bounded exercise to inspect both products against the records your reviewers need.

Arc publishes this source-based protocol and has a commercial interest in teams choosing Arc. No Flow or Arc run has been executed for this article. The records below are fictional teaching inputs. The calculation and reference disposition are authored expectations, while all product-execution outcomes remain unobserved.

The shared comparison definition uses the same values and IDs. This page owns the detailed procedure, expected artefacts and evidence record so a team can use it without treating the example as customer or product proof.

Prepare the fictional B1 input set

B1 has payload demand of 18 W, other demand of 36 W and supply of 59 W in the same illustrative peak operating condition. Total demand is 54 W and margin is +5 W. Define B1 as the accepted state and keep the proposed change separate.

Fictional Flow Engineering and Arc change protocol FT-P03: baseline B1 records and expected relationships. Power values are in watts (W). No product run or test result is supplied.
RecordProtocol contentRelationship/evidence context
SYS-PWR-001Total peak demand must be ≤59 W.Linked to AN-PWR-01.
PAY-PWR-014Payload demand is 18 W in B1, proposed 24 W.Linked to TEST-PWR-02. No additional payload requirement cap is specified.
IF-PWR-003Payload electrical interface is 28 V ±1 V.Linked to TEST-IF-03.
PAY-THM-005Plate temperature must be below 50 °C.AN-THM-04 is available, but the relevant thermal relationship is deliberately incomplete.

Retain the IDs, units, owners and relationship meanings in each evaluation. Record source and revision fields for the fictional package. If you add a procedure, result or test article to run the exercise, label it as an additional input rather than implying that this protocol supplied a completed test.

The 18 W number is the baseline demand input, not a separate limit on payload draw. The system’s unchanged 59 W total-demand obligation supplies the power acceptance condition. The available thermal analysis does not establish a complete relationship or a verified temperature result.

Apply the 18 W to 24 W proposal

Increase payload demand to 24 W while holding other demand, supply and the illustrative operating condition fixed. Use the transparent calculation below. It is a simplified demand calculation, not a validated spacecraft power or thermal model.

Fictional payload power calculation for B1 and the 18 W to 24 W proposal: watts (W), other demand fixed at 36 W and supply at 59 W. Authored arithmetic, not product output.
QuantityB1Proposal
Payload demand18 W.24 W.
Other demand36 W.36 W.
Total demand18 + 36 = 54 W.24 + 36 = 60 W.
Supply59 W.59 W.
Margin: supply − demand59 − 54 = +5 W.59 − 60 = −1 W.

The proposal exceeds SYS-PWR-001 by 1 W under the stated assumptions. It cannot enter the accepted baseline as a feasible design without rework or a separately authorised change to the governing obligation. Retain the calculation with its assumptions and owner.

The arithmetic does not establish interface voltage regulation, plate temperature or a complete physical dependency model. Those are separate engineering questions whose records and evidence must remain visible.

Keep the proposal and accepted state distinct

  1. Identify B1, its record revisions and the relationship inventory before editing.
  2. Create the proposed payload change through the agreed branch or controlled-proposal route.
  3. Inspect the field, text and relationship differences and record the reason for change.
  4. Confirm B1 still identifies the accepted 18 W case while the proposal remains unaccepted.
  5. Capture the product version/date, permitted roles and any assistance used during the run.

Flow’s Branching page documents isolated branches, differences, required reviewers and immutable baselines. Arc’s change-control capability covers branches, discussion, review and merge under the configured authority model. These are documented mechanisms to inspect, rather than completed steps in this publication.

This Flow Engineering requirements traceability exercise checks relationship meaning and completeness, alongside the change’s numerical impact.

Follow SYS-PWR-001 to AN-PWR-01, PAY-PWR-014 to TEST-PWR-02 and IF-PWR-003 to TEST-IF-03. For each relationship, retain endpoints, revisions, meaning and applicability. Ask what the relationship actually constrains or verifies.

Then inspect PAY-THM-005. AN-THM-04 exists, but the relevant thermal relationship is deliberately incomplete. The expected finding is unresolved thermal context requiring investigation. Do not silently add the link or mark the plate requirement verified simply to complete the graph.

A missing trace does not mean there is no physical effect. An agent’s inferred link is a proposal for engineering review, not evidence that the analysis applies. Arc’s traceability and gap views expose stored context while engineers maintain relationship meaning. Flow’s documented graph and agents should face the same incomplete input.

Use the existing change-impact guide for the wider dependency sweep. Keep thermal closure open even after the power conflict has a clear disposition.

Record the expected engineering disposition

Authored reference disposition: return the 24 W proposal for rework because the power limit is exceeded, retain B1 and assign a feasible-option task to the payload owner. The systems owner assesses the power/interface consequences. The thermal owner investigates the incomplete dependency. The test engineer assesses evidence applicability.

This reference answer is not a product-generated rejection or approval. In an executed run, retain the actual named decision makers, reviewed proposal, rationale, disagreement and open actions. Arc records attributable decisions against reviewed context. Flow describes required reviewers and recorded baseline approvals. Inspect how both setups retain a returned proposal and its unresolved work.

Check authority separately from identity. The person who can edit or administer records may not be the person authorised to accept the engineering decision. Inspect exception paths and use the decision-record fields to retain scope and rationale.

Keep historical evidence in its original scope

The protocol supplies verification references, not completed results. If your evaluation adds an earlier result for B1, retain its requirement revision, procedure revision, success criteria, execution date, responsible person, test article and as-tested configuration.

Ask the verification owner to record one of three outcomes: reuse is justified for a defined scope, an additional analysis is needed, or new verification is required. Retain the reason and assumptions. An old passing result does not become evidence for the 24 W proposal through a record edit.

Arc connects verification plans, executions, results and evidence to requirements and configurations. Flow documents connected tests and separate verification status/validation stage. The evaluation should inspect the result provenance and configuration fields in each selected setup, with the same acceptance condition.

Separate protocol inputs from product outputs

Execution status: unexecuted. No screenshots, product exports, branch differences, role captures or review records are presented as demonstrated outcomes. The arithmetic and reference disposition are on-page authored resources.

For a future run, retain an inventory of the actual outputs: baseline and proposal references, relationship view, permissions, review disposition, evidence applicability and the package supplied to a reviewer. Flow documents branch exports as PDF, DOCX and CSV. Confirm the contents of the selected export and any live records the reviewer also needs.

Label each artefact protocol input, observed product output or reviewer judgement. Record assistance and unresolved limitations. Do not replace an expected field with a fabricated screenshot or mark a vendor-documented capability as passed without an actual observation.

Ask another reviewer to reconstruct the decision

Give an uninvolved reviewer the package produced by an actual run. Ask them to identify B1, the 18 W to 24 W proposal, the 54 W to 60 W total, the +5 W to −1 W margin, the thermal gap and the returned-for-rework disposition.

Then ask which result applies to which requirement and configuration. Record what the package contains, what requires application access and what the reviewer needs to ask. A readable report can be useful without carrying every relationship, review or evidence record. Keep any missing mandatory context unresolved.

Complete this evaluation evidence record

Original resource: evaluation record, FT-P03. Its current entries state what this publication supplies. In an executed evaluation, replace them with dated artefact references and owner judgements. Keep the fictional calculation separate from observed product behaviour.

Unexecuted Flow Engineering and Arc evaluation record FT-P03: expected artefacts, responsible roles and current evidence limits. No demonstrated product outcome is marked as passed.
CheckExpected inspectable artefactCurrent evidenceResponsible roleCurrent limitation
Accepted baselineB1 IDs, revisions and relationship inventory.Fictional on-page definition.Systems owner.No product baseline capture.
Power proposal24 W payload, 60 W total, −1 W margin and unchanged 59 W obligation.Authored arithmetic.Payload and systems owners.Fixed illustrative condition, no product execution.
Controlled changeProposal differences, unchanged B1 and role permissions.Expected checks only.Systems owner.No branch or permission artefact.
Thermal dependencyVisible incomplete relationship and assigned investigation.Deliberate protocol gap.Thermal owner.Physical applicability remains unresolved.
ReviewNamed disposition, reviewed context, rationale and open work.Authored return-for-rework reference.Milestone owner and reviewers.No actual product review decision.
VerificationResult provenance, revisions, configuration and applicability decision.Verification references only.Test engineer.No executed result or reuse judgement.
ReconstructionOutput inventory and independent reviewer explanation.No observed package.Uninvolved reviewer.No export or reconstruction result.

Use the milestone review for the owner’s fit decision and the configuration guide for a variant extension. A clear trace and recorded proposal support the decision. The named authority still owns acceptance and the unresolved thermal investigation.

Frequently asked questions

Does a clean trace prove all physical dependencies are modelled?

No. A trace shows the relationships stored in the record model. This protocol deliberately leaves the thermal relationship incomplete while PAY-THM-005 and AN-THM-04 exist. Engineers need to investigate physical dependencies beyond the linked path before accepting completeness.

What happens to the old test result?

Keep its original requirement and procedure revisions, result provenance and as-tested configuration. It remains historical evidence for that condition. The responsible engineer decides whether it supports the proposal, can be reused with a documented justification or needs new verification.

Was the exercise run in Flow or Arc?

No. This article supplies a fictional evaluation protocol, authored arithmetic and expected evidence checks. It reports no executed Flow or Arc run, screenshots, product exports, review record, timing or comparative performance result.

Can AI approve the changed baseline?

AI can help surface context, check records and propose work within configured permissions. The named engineering authority owns the controlled baseline decision. Inspect permitted actions, required reviewers and exception paths, then retain the actual decision against the reviewed proposal.

Why does the 24 W proposal need rework before the thermal question is resolved?

With other demand fixed at 36 W and supply at 59 W, the proposal totals 60 W and leaves −1 W margin. It exceeds SYS-PWR-001 by 1 W under the stated assumptions. Return the proposal for rework and retain B1. That arithmetic does not resolve PAY-THM-005 or the deliberately incomplete relationship to AN-THM-04.

Move faster without compromising engineering rigour.

Book a demo using the fictional power proposal below. Follow B1, the changed demand, the review disposition and the evidence configuration while keeping the thermal dependency open.