Plans and evidence
These are directions we’re preparing to explore. None has a published research result here yet.
Barcode and label workflows come first, followed by automation and hired company builds. Practical open tools and data checks are the nearest research work; longer studies follow checked examples. All studies and samples below are in development, with no release dates to share.
In development
Status: existing barcode and label tools provide a starting point. A separate utility with published source and reproducible checks is planned.
Next: build a small file checker with sample inputs, expected results and instructions. Check the right to share every part.
In development
Status: a possible later study; no material has been discovered or tested.
Next: reproduce a small published model and show how its assumptions affect the result. A model does not establish a safe chemical process or a material’s real properties.
In development
Status: a small energy and storage model is planned. It has not been built or checked.
Next: compare made-up demand and generation data with and without storage, and check the arithmetic. This will not establish battery safety, electrical design or installation requirements.
In development
Status: a later idea for a simple navigation model; no robot or controller has been tested.
Next: show a route through a small map and record the cases where it fails. A simulated route cannot prove a robot safe to use.
In development
Status: a later idea for organizing research papers; no evidence tool has been validated.
Next: check a small set of permitted sources and link each summary to its source passage. This is for organizing literature, not diagnosis, treatment or medical advice.
In development
Status: a possible later direction for drawings, instructions and example software; no device has been built or tested.
Next: write a small sensor specification and an example that imitates its readings. Physical performance would need separate testing.
In development
Status: a small data-cleaning study is planned; there is no checked forecast or field result.
Next: flag missing readings and mismatched units in sample files, then show the cleaned results and remaining uncertainty. A chart alone cannot establish a cause or a new prediction.
In development
Status: a planned way to share methods, source files, checks and results, including attempts that do not work. No research report is being presented as complete.
Next: publish a reproducible sample after its sources, permissions and checks have been reviewed. Sharing a report does not make it peer reviewed.
In development
Planned first. Map codes, label text and quantities, review errors and prepare a label print file. Compare expected and counted stock, keeping leading zeros, duplicates and missing rows visible.
Still needed: a working example, known-answer files, code read-back, layout/export checks and instructions. Printer tests remain separate.
In development
Planned second. Search made-up office instructions and show where an answer comes from. Requests would create draft checklists and email text.
Still needed: checked answer examples and failure cases. The sample would not send email or change sign-in accounts.
In development
Planned third. Compare demand, generation and storage using made-up data, clear units and visible assumptions.
Still needed: a working model and a hand-calculated reference to check its results. It would show energy quantities, not predictions about money.
A later sample can set technical notes side by side, try a small model and list what still has to be checked. This is not medical, legal or financial advice, and a model is not a promise about health, the law or money.
Ask about a research direction