[Q&A] What is unclear, ambiguous, or underspecified in the Sal-Meter project?

[salpida-foundation]

This thread is open for all questions, uncertainties, and points of ambiguity
related to the Sal-Meter Open Competition.

If something feels unclear, underspecified, or difficult to interpret,
that feedback is valuable signal for improving the documentation.

---

You may ask about (examples)

• CAIS technical boundaries and compliance requirements
• What must vs may be implemented in a Sal-Meter prototype
• Validation logic, reproducibility, and measurement criteria
• Documentation and openness expectations (especially Track C)
• Team composition or participation pathways
• How canonical DOI documents relate to GitHub materials
• What is explicitly out of scope

This list is not exhaustive.

---

Important notes

• There are no bad questions
• Lack of clarity is treated as a documentation issue, not a participant issue
• Answers here may result in:
  • Clarifications in README
  • Updates to non-canonical guides
  • Explicit boundary tightening in future canonical documents

---

How to ask a good question (optional)

If helpful, include:

• What document or section you read
• What interpretation felt ambiguous
• What decision you are blocked on (if any)

Short questions are perfectly fine.

Ask freely.

[salpida-foundation]

Here is an example of the kind of uncertainty we are hoping to surface:

• “We are interested, but it is unclear how strict the CAIS compliance boundaries are at the prototype stage.”
• “It’s not yet clear to us what level of validation is expected for Phase 1 versus later phases.”
• “We are unsure how IP is handled if our approach diverges technically but remains CAIS-compatible.”

If you have similar questions or concerns, even in rough form, please feel free to share.