FAQ

Can I commit directly to main?

No. Open a pull request, even for documentation. The review and automated checks are part of the delivery record.

When should I create an issue?

Before work starts, unless you are mitigating an active incident. For an incident, create or backfill the issue as soon as service is stable.

How large should a PR be?

Small enough that a reviewer can understand its intent and risk in one focused session. Prefer enabling PRs, feature flags, and follow-ups over a large all-at-once change.

Which CRS should I use?

Use the project’s documented CRS. For interchange and web APIs, Spatialnode defaults to EPSG:4326. Web-map rendering commonly uses Web Mercator internally; make that transformation explicit.

Can I put a sample secret in .env.example?

Only fake, unmistakably non-functional values. Include every variable name, purpose, and safe example; never paste a real key, token, client secret, or client data.

A check is failing but my change is unrelated. What now?

Investigate and report the failure in the PR. Fix it when the fix is contained; otherwise create a linked issue and ask the tech lead before merging around it. Required checks remain required.

How do I request production access?

Ask the project owner through the approved access channel with the environment, role, reason, and expiry needed. Spatialnode grants least privilege and reviews access regularly.

Where do architecture decisions go?

Record consequential, durable decisions in the product repository’s docs/adr/ directory. Include context, decision, alternatives, and consequences.