# Hypothetical engineering source packet

All people, organizations, records, dates, results, and confirmation entries in this packet are invented. No actual engineering tests, factual confirmations, or legal reviews occurred. These sample records illustrate source-to-field tracing for an invention disclosure. They do not establish inventorship, ownership, patentability, or readiness to file.

## Source register

| ID | Record | Version and date | Fictional record owner |
| --- | --- | --- | --- |
| S1 | Project brief | Version 1, April 3, 2026 | Priya Rao |
| S2 | Controller design note | Version 2, April 9, 2026 | Julian Chen |
| S3 | Bench-test report | Version 1, May 2, 2026 | Morgan Ellis |
| S4 | Contribution and development log | Version 1, May 4, 2026 | Priya Rao |
| S5 | Project administration and event log | Version 1, May 4, 2026 | Alex Park |

## S1: Project brief

### §1. Problem and baseline

The fictional Cabinet cooling project concerns an industrial electronics cabinet with a replaceable inlet filter and a fan. The team's existing approach is scheduled filter replacement. The team knows that baseline from its internal cabinet design; no external patent documents or publications are included in this packet.

A pressure reading across the filter while the fan operates can reflect filter restriction or an offset in the pressure sensor. The proposed approach aims to distinguish those conditions in its maintenance indication. This is a project objective, not a comparative performance or novelty result.

### §2. Proposed approach and constraints

Priya proposed sampling differential pressure while the fan is stopped, then again at a known fan speed. The stopped-fan sample would serve as an offset reference. A large stopped-fan value would indicate the need for sensor review instead of a filter-maintenance alert.

The bench rig can pause the fan. Whether a live cabinet can safely pause its fan, for how long, and under which thermal loads is unresolved. This record supplies no live-cabinet thermal assessment.

### §3. Intended use and business context

Intended use is a filter-maintenance indication in industrial electronics cabinets. The team proposes a live-cabinet evaluation after its operating limits are addressed. Alex Park is the fictional business owner. No cost, evaluation schedule, commercial value, or production reliability conclusion has been approved.

## S2: Controller design note

### §1. Inputs and components

The bench embodiment includes a 24-volt fan, a fan-speed signal, 1 differential-pressure sensor with ports on opposite sides of the filter, and a controller. Pressure is measured in pascals (Pa), and fan speed in revolutions per minute (RPM). Output states are maintenance alert, no maintenance alert, and sensor review. Display location is optional.

### §2. Operating sequence

1. With the fan stopped and pressure settled, acquire a pressure sample called the stopped-fan reading.
2. If the reading is outside ±5 Pa, raise the sensor-review flag and suppress the filter-maintenance alert. This is a diagnostic rule for the bench embodiment, not proof of the cause of the reading.
3. Otherwise, run the fan at the commanded speed and acquire the running pressure reading.
4. Subtract the stopped-fan reading from the running reading to obtain corrected pressure.
5. Compare corrected pressure with the threshold entry for the measured fan speed.
6. Apply the persistence periods in §3 before changing the maintenance-alert state.

The central proposed elements are pressure sampling, comparison logic, and the separate output states. The team has not established that these elements are legally essential claim limitations.

### §3. Implemented parameters

The only supplied calibration entry is for 2,000 RPM:

| Parameter | Bench setting |
| --- | --- |
| Maximum acceptable magnitude of stopped-fan pressure | 5 Pa |
| Maintenance-alert threshold | Corrected pressure above 50 Pa for 30 seconds |
| Maintenance-alert clearing threshold | Corrected pressure below 40 Pa for 60 seconds |

Julian proposed the persistence periods and implemented the state logic on April 9, 2026. The different trigger and clearing thresholds reduce repeated state changes around a single boundary in this design. No field-performance result is supplied.

### §4. Variants and unresolved constraints

- **Bench-tested embodiment:** the listed 24-volt fan, differential sensor, and controller at 2,000 RPM.
- **Proposed embodiment:** a calibration table with thresholds for additional fan speeds. Other-speed values have not been supplied or tested in this packet.
- **Speculative embodiment:** 2 separate pressure sensors, one on each side of the filter, replacing the differential sensor. This version has not been built or tested.
- **Optional element:** display location. The maintenance state could be presented locally or reported to a cabinet controller.
- **Unresolved conditions:** safe fan-pause operation in a live cabinet, tube leakage, long-term drift, and sensor behavior under other temperatures or airflow conditions.

## S3: Bench-test report

### §1. Setup

On May 2, 2026, Morgan ran the fictional tests in Lab A on 1 enclosure with a replaceable filter, the 24-volt fan at 2,000 RPM, 1 differential sensor, and the controller described in S2. Ambient temperature was 23°C. A restriction screen represented a restricted-flow condition. An injected sensor offset represented 1 diagnostic case. This is an invented instructional dataset.

### §2. Observations

| Case | Stopped-fan reading | Running reading | Corrected value or diagnostic state | Recorded response |
| --- | --- | --- | --- | --- |
| Clean filter | 0 Pa | 20 Pa | 20 Pa | When started from the alert state, the alert cleared after 60 seconds below 40 Pa. |
| Restriction screen | 0 Pa | 65 Pa | 65 Pa | The maintenance alert triggered after 30 seconds above 50 Pa. |
| Clean filter with injected +8 Pa offset | 8 Pa | 28 Pa | Sensor-review state; maintenance comparison suppressed | The sensor-review flag appeared and the filter alert was suppressed. |

### §3. Evidentiary limits

Only 1 rig, 1 fan speed, and 1 ambient temperature are represented. The packet does not report repeated-run statistics, other-speed calibration, tube-leak tests, live-cabinet thermal safety, long-term drift, production reliability, or field comparisons against scheduled maintenance. It does not establish the cause of every possible large stopped-fan reading. The team expects more informative maintenance signals, but that expectation is not a demonstrated general benefit.

## S4: Contribution and development log

### §1. People and reported activities

All listed people are fictional employees of Example Engineering Group. These descriptions record activities for counsel's review, not legal inventorship.

| Person and work contact | Role | Reported contribution or activity | Recorded date and source |
| --- | --- | --- | --- |
| Priya Rao; priya@example.invalid | Controls engineer | Proposed stopped-fan offset sampling and the distinct sensor-review condition. | April 3, 2026; S1 §2. |
| Julian Chen; julian@example.invalid | Firmware engineer | Proposed persistence timing and implemented the state logic and listed parameters. | April 9, 2026; S2 §§2–3. |
| Morgan Ellis; morgan@example.invalid | Test engineer | Assembled the specified rig and ran the specified tests; no separate technical idea is reported in this log. | April 20 and May 2, 2026; S3. |

The submitter asks counsel to consider Priya and Julian as possible inventors. Morgan's full activity description is included so counsel can ask further questions if appropriate. No one is excluded from counsel's review by the tentative list. Earlier unrecorded discussions or contributions are unknown.

### §2. Development chronology

| Date | Event | Location and record |
| --- | --- | --- |
| April 3, 2026 | Problem, baseline, and sampling proposal recorded. | Lab A; S1. |
| April 9, 2026 | Controller design revised and listed state logic implemented. | Lab A; S2 version 2. |
| April 20, 2026 | Morgan assembled the bench rig. | Lab A; this development log. |
| May 2, 2026 | Morgan ran the reported bench cases. | Lab A; S3. |
| May 4, 2026 | Priya prepared disclosure HYP-026 version 1. | Lab A; S5 §1. |

These are the dates reported in the sample records. No earlier idea date, legal conception date, reduction-to-practice conclusion, or priority claim is asserted.

### §3. Sample factual-confirmation entries

The entries below are simulated, not actual signatures or confirmations. Each uses the statement: “I have reviewed the technical description, my recorded contribution, and the development and disclosure events within my knowledge. My corrections and uncertainties are recorded in the open-question log. This confirmation concerns factual accuracy, not a legal inventorship determination.”

| Person | Simulated date and factual scope | Corrections or limits |
| --- | --- | --- |
| Priya Rao | May 4, 2026; confirms sampling description and her reported contribution. | Live-cabinet fan-pause thermal limits remain unresolved. |
| Julian Chen | May 4, 2026; confirms implemented thresholds, persistence periods, and his reported contribution. | Other-speed calibration is pending and must not be described as tested. |
| Morgan Ellis | May 4, 2026; confirms the listed rig and bench observations within his knowledge. | No general performance claim; April 28 vendor documents require follow-up. |

## S5: Project administration and event log

### §1. Intake metadata

| Field | Sample entry |
| --- | --- |
| Title | Pressure-aware filter-maintenance controller for an electronics cabinet |
| Record ID and version | HYP-026, version 1 |
| Project | Cabinet cooling |
| Submitter and contact | Priya Rao, controls engineer; priya@example.invalid |
| Employer | Example Engineering Group, fictional |
| Submission date | May 4, 2026 |
| Internal access designation | Restricted to the project and IP team |

### §2. Business, funding, agreements, and related work

Alex Park, fictional product manager, alex@example.invalid, is the business owner. The project ledger reports internal project funding and does not list grants, sponsors, or outside collaborators. This ledger entry is not an ownership or compliance conclusion. Purchased sensor terms have not been provided. Vendor agreement references are unresolved.

The proposed live-cabinet evaluation has no approved cost or schedule. No external patent or publication references have been supplied, and no prior-art search is reported. Related-work collection is assigned to the project team for counsel's scoped search, without representing that collection as an absence-of-prior-art finding.

### §3. External-event facts

| Date and state | Recipient and channel | Material and access facts | Remaining question |
| --- | --- | --- | --- |
| April 28, 2026, reported actual event | Morgan sent an email to a fictional outside machining vendor; final recipient identity is not provided. | An assembly drawing was attached. The sent file and confidentiality-agreement reference have not been supplied. | Obtain the exact drawing, email, recipients, and agreement. Legal effect has not been assessed. |
| May 15, 2026, planned event | Customer demonstration; recipients and channel are pending. | Final slides and demonstration content are pending. No confidentiality terms are recorded. | Obtain the final materials, recipient list, and access terms for counsel before the event. |

The team reports no publication, sale, or offer in this event log. It has not reconciled every participant's calendar or correspondence, so the log is not a complete event-history confirmation.

### §4. Open-question log and handoff

| Gap | Needed answer or record | Owner | Requested response date |
| --- | --- | --- | --- |
| Operating limits | Live-cabinet conditions permitting a fan pause and thermal assessment. | Priya | May 6, 2026 |
| Untested embodiments | Other-speed calibration table and any corresponding reports. | Julian | May 6, 2026 |
| Development history | Earlier discussions or technical contributions, with dated records and individual accounts. | All contributors | May 6, 2026 |
| Third-party terms | Purchased-component terms and vendor agreements. | Alex | May 5, 2026 |
| External events | April 28 sent material, recipients, and access terms; May 15 final content, recipients, and access terms. | Morgan and Alex | May 5, 2026 |
| Legal next step | Contribution, disclosure, jurisdiction, and rights questions requiring follow-up before a scoped search or drafting assignment. | Assigned patent counsel | Upon handoff |

Counsel recipient is the organizational IP intake queue; no individual is assigned. Handoff is requested May 4, 2026. Counsel review has not occurred. No prior-art search or application drafting is authorized in this example's organizational process. Counsel confirmation before those assignments is a recommended workflow control for the example, not a universal legal prerequisite or an enforced platform gate. No patentability, ownership, inventorship, filing-readiness, or deadline conclusion is recorded.