01 / Observe
Open Observe to paste or import a UTF-8 CSV file. The first row must be time,value. Times are finite numbers expressed in seconds and must increase strictly. Values are finite numbers using the unit of your measurement.
time,value
0,0.12
0.1,0.24
0.2,0.18
- Paste a CSV or select Import CSV. Files are limited to 48 KB, with 2 to 2,000 measurements.
- Select Analyse data. Inspect individual samples using the trace or the accessible sample slider.
- Review the minimum, maximum, mean, RMS and peak-to-peak value. These are calculated from the imported samples.
- Select Download CSV to export validated numeric data. Save to account is a separate, explicit action.
The synthetic example is a demonstration trace. Measurement units, calibration and uncertainty are your responsibility. This tool does not connect to test hardware or continuously collect data.
02 / Devtools
Open Devtools to describe a system as JSON. Every node requires a unique id, a readable label and a type. Each directed edge specifies existing from and to identifiers plus a protocol.
{
"name": "Sensor acquisition",
"nodes": [
{ "id": "sensor", "label": "Sensor", "type": "sensor" },
{ "id": "mcu", "label": "Controller", "type": "controller" }
],
"edges": [
{ "from": "sensor", "to": "mcu", "protocol": "I2C" }
]
}The validator accepts a directed acyclic graph with up to 32 nodes and 64 connections. Self-connections, missing references and cycles are rejected. Describe feedback loops as distinct processing stages when preparing an acyclic overview.
Validate & render updates the diagram and connection table. Copy JSON and the JSON or TypeScript downloads validate the current input again. A TypeScript export contains data and interface definitions, not executable device firmware. Pasted content is never evaluated.
Structural validity is not electrical compatibility. Verify voltage domains, bus pull-ups, bandwidth, scheduling and fault behaviour against the relevant component documentation.
03 / Deploy, mau!
Open the release workspace to prepare a handover manifest. Enter the project name, version, delivery target and artifact or test references. Review all four gates: scope, validation, security and handover.
Check release readiness requires valid fields and every gate to be completed. The ready state is based on your declarations. Editing any field resets it to draft. Download manifest exports the release with its status and deploymentPerformed: false.
This workspace does not build source code, store credentials, provision infrastructure or deploy to a hosting provider. Use your existing release and hosting workflow to publish the actual artifact.
Storage and privacy
Parsing, graph layout, calculations and downloads happen in your browser. Validated inputs are kept in this browser tab so the homepage preview and full workspace share the same data. This is session storage, not an account upload. Use Clear in the homepage tool preview to remove a tab record, and download any work you need to keep. Unvalidated edits can be lost when you navigate away.
Save to account is available after signing in with a verified 4TECH account. Save to account, Update saved record and Save a copy explicitly upload the tool document to account storage. Your saved records are separated by account and protected by Firestore access rules. Cloud availability errors appear in the workspace; they do not count as successful saves.
Open loads a saved record for editing. Update saved record replaces it, while Save a copy creates a separate document. Refresh saved records reconnects after a cloud error. Delete removes the selected saved document after confirmation. Local exports are separate copies on your device. Do not paste credentials, private keys or confidential data that you do not have permission to process.
Client Space · Privacy policy · Terms