Skip to content
A personal experiment · alpha · code not public yet · no offer, no support Project status →

Feedback and usage reports

Vaicoa sends nothing by default. The only thing a core fetches on its own is the signed release feed, without a key and without an account (air-gapped cores import it by hand). Two commands can send something to the project, and only when you run them, after you have seen exactly what would be sent.

Terminal window
sudo vaicoa-core usage report --preview # shows exactly the JSON that would be sent
sudo vaicoa-core usage report --out report.json # writes it to a file
sudo vaicoa-core usage report --send --file report.json # sends exactly these bytes
  • What is in it: whole numbers in coarse ranges. No names, no hosts, no parameters, no IP addresses. Your own actions appear only as org.*.
  • Exactly these bytes: the signature differs on every run. To be sure that what you read is what is sent, write the file with --out, read it, and send it with --send --file.
  • Record: every share is in your own audit as usage.shared with the report’s digest.
  • Reminder: off until you set usage: {reminder: monthly} in core.yaml (or agree during init --quickstart). usage remind later means “not this time”, usage remind never means “never again”. usage reset-id starts a new series with a new installation id and key.
  • In the app: if the reminder is on, owners are asked once a month; “Send …” first shows the report, and it is sent only with “Send now” and only if it has not changed since the preview.

After eight to twelve weeks of measured improvement, the core can draft a case study from its key figures, its reports and your baseline measurement:

Terminal window
sudo vaicoa-core usage casestudy --since 90d --baseline baseline.yaml \
--own-operation --out casestudy.md
sudo vaicoa-core usage casestudy --share --file casestudy.md

The draft stays local, readable only by root. What the core cannot measure is marked “missing”, never estimated, and numbers are rounded against you. --share first checks the text for names, hosts, environments, IP addresses, URLs and mail addresses the core knows and shows you exactly what will be sent; it sends only after you type “send”, and the audit records usage.casestudy_shared. Names the core does not know it cannot find, so read it once more yourself. --revoke DIGEST sends a signed revocation, and the receiver deletes the case study.

Questions, ideas and reports of what did not work are welcome through the contact section. Security issues go privately to security@mitjamartini.com. There is no diagnostic bundle command yet; if you send logs, read them first and remove what you do not want to share.