|
Download COMMERCIAL_EXTENSION.md from RegalFire/Scientific-Code-Troubleshooting: direct link, hf CLI and curl.
- Browser
- Download file 1.41 kB
-
https://huggingface.co/datasets/RegalFire/Scientific-Code-Troubleshooting/resolve/main/COMMERCIAL_EXTENSION.md
- Command line
-
hf download hf://datasets/RegalFire/Scientific-Code-Troubleshooting/COMMERCIAL_EXTENSION.md
-
curl -L -o COMMERCIAL_EXTENSION.md https://huggingface.co/datasets/RegalFire/Scientific-Code-Troubleshooting/resolve/main/COMMERCIAL_EXTENSION.md
1.41 kB
| # RegalFire — Commercial Extension | |
| Ideal buyer: Scientific software and research assistant teams. | |
| Business problem: Real scientific troubleshooting with literal code and attributed community answers. | |
| Custom private variant: Permitted notebooks and issue reports with separately agreed executable or expert-reviewed checks. | |
| Client inputs: permitted sources, schema, target model/agent API, failure definitions, oracle or qualified reviewers, privacy/retention requirements, deadline and measurable acceptance criteria. | |
| Validation approach: separate generation and verification, strict schemas, source relations, grouped splits, negative cases and deterministic checks where feasible. Expert or executable labels require separate verification. | |
| Example pilot: proposed 50–150 cases in one use case, 3–5 working days after agreed inputs. This is a scoping estimate, not a past delivery claim. PRICE = QUOTE. | |
| Delivery: JSONL/CSV, schema, provenance, validator where applicable and QA report. | |
| Customizable: schemas, permitted private source integration, hard-case families, private holdout, acceptance tests and update cadence. | |
| Limits: Community answers, acceptance and scores are not scientific truth or executable success labels. Public CC BY-SA obligations remain; confidential data must come from permitted private sources. | |
| Omar Soliman · RegalFire · ootiris@gmail.com | |