sandbox-code-guidelines

name	sandbox-code-guidelines
description	Guidelines for quick C# experiments in `sandbox/DotnetFiles/` across Ol's full domain: dependency graphs, OSS license evidence, SPDX expressions, reconciliation, package/source metadata, caches, reports, policy ideas, performance probes, and CLI-adjacent behavior.

Sandbox Code Guidelines

IMPORTANT: Never use dotnet script or dotnet-script command. This project does NOT use dotnet-script.

If you need to create a .cs file to verify something, you can create it in the sandbox/DotnetFiles/ folder and run it.

Ol is a transitive OSS license resolver and future policy-enforcement tool. The sandbox is not limited to SBOM parsing. Use it for isolated experiments involving:

• component identity and root/direct/transitive dependency relationships
• SPDX identifiers, exceptions, expressions, and normalization
• license candidates, evidence reconciliation, and status precedence
• package registry or source repository response normalization
• cache keys, hashing, serialization, concurrency, and retry behavior
• report shaping, grouping, sorting, and policy-evaluation prototypes
• allocation, generated-code, Native AOT, and BCL API feasibility checks

Use the smallest boundary needed for the question. Reference Ol.Core when validating reusable domain behavior; a standalone BCL-only file is preferable when no Ol type is needed. CLI orchestration and user-visible behavior belong in repository tests once the experiment establishes the approach.

See dotnet run details here: https://github.com/dotnet/sdk/blob/main/documentation/general/dotnet-run-file.md

• For a standalone C# file (without .csproj):

#:sdk Microsoft.NET.Sdk


 System.Text;
 Ol.Core;