A public reference. Not a confidential channel.

1. Keep it lawful and safe

Share only information you are entitled to make public. Do not submit classified information, controlled unclassified information, protected records, nonpublic government material, operational details, privileged communications, or information restricted by an order or duty.

Do not post names, contact details, identifying unit information, case numbers, medical information, or other facts that identify a person or active matter. Generalize your question. No file uploads or private case intake are provided.

No threats, harassment, personal accusations, impersonation, spam, unsolicited promotion, or promises of a legal outcome. Do not coach anyone to conceal, destroy, falsify, or unlawfully disclose information.

2. Show your work

Label personal experience and opinion. For legal or regulatory claims, cite a public source and identify the relevant page or paragraph and version or date. Corrections and source submissions require a citation.

A government-domain label is a technical description of a link, not verification. Sources may be superseded or inapplicable. A useful vote is feedback, not an accuracy rating.

3. Every contribution is reviewed

All posts and replies start as private, pending submissions. Only the author and publisher can view them before approval. The publisher can approve, decline, or later withdraw material and can pause posting for an account or guest browser session. Automated screening provides signals only.

Approval permits publication; it does not endorse every assertion. Owner-reviewed knowledge has an additional source review and an editorial note. Contributions never rewrite the Field Reference automatically. Submit a new correction when circumstances change; approved text cannot be silently edited.

Use “Report a concern” on an approved contribution to send a private report. Reports are not emergencies and there is no guaranteed response time. If you need to correct or withdraw your own post, use the report form. For a pending submission, wait for review or send a new, clearly identified withdrawal request through the contribution form without repeating sensitive content.

4. Ownership and permission

The publisher retains editorial control of this site. Contributing, voting, or subscribing does not give anyone ownership or editing rights. Contributors retain rights in their own original content.

By submitting, you grant the publisher a nonexclusive permission to store, review, display, format, and back up your contribution for this publication. You confirm that you have the right to share it. External republication of your original material is not automatic; separate permission should be obtained where needed. Public-domain and third-party source material retains its existing status and terms.

Hosting, X, Substack, and other providers operate their own services under their own terms. Site control does not mean ownership of those platforms. The owner can export community records; contributors do not gain access to that export.

5. Privacy and data use

You may submit posts, replies and concern reports without an account or email. Choose a display name; approved contributions label it as “Guest”. Names are not verified, unique or reserved. Do not impersonate another person or use a staff title.

When you submit as a guest, a necessary browser cookie gives access to your private submission status for 30 days. The server stores a hash of that random receipt, an expiry time and a guest member identifier. It does not store the receipt itself. The cookie is not used for analytics or advertising. Anyone using that browser profile can access its submissions; clearing cookies, switching devices or ending private browsing loses access. There is no email recovery. Expired receipts stop working immediately and are removed in batches when new guest sessions are created; existing contributions remain stored.

ChatGPT sign-in is optional for existing member participation and is retained for owner administration and useful votes. It supplies a per-site account identifier and account claims to the hosting service. The community stores the account or guest identifier, a generated alias or chosen guest display name, submissions and citations, review status, votes, reports, posting restrictions, timestamps, and an audit record. It does not publish your account email.

Approved posts, aliases, source links, review notes, reply counts, and usefulness totals are visible to the site’s permitted audience. If the site is later public, these may be indexed, copied, or shared by others. Pending and declined submissions, reports, member identifiers, and owner exports are not part of public feeds.

The publisher uses stored records to moderate and improve the reference. No AI model training, advertising tracker, embedded social feed, or automatic transfer of submissions to X or Substack is configured in this site. Providers may process access and security data under their own policies. External links take you to those providers.

Submission, moderation and member records are retained until the publisher removes them. Browser receipt access expires after 30 days; expiry does not delete submissions. Expired hourly limit counters are removed in batches when new guest sessions are created. Posting limits apply both per session and across guest contributions to manage abuse; they do not establish one person per session. The publisher should establish a retention policy and contact address before public launch. Withdrawal from display does not erase audit records, backups, or copies made by others.

Audience measurement

We use Plausible to understand use of the public Field Reference, Cases & Analysis index, publication channels, community index and rules. We count page views and clicks on a fixed list of publisher-selected sources and downloadable references. Community discussions, submission forms, owner pages and sign-in routes are excluded. Query strings, page fragments, private content and account identifiers are not sent. Referrers are reduced to their domain.

Plausible receives the connection’s IP address and browser information, uses them to derive a daily visitor estimate and approximate location, and discards the raw IP and user-agent values under its data policy. It does not use cookies or a persistent visitor identifier. This site sends no community identities or messages to Plausible and uses no session recording, form capture, advertising profile, or cross-day visitor matching. Collection is disabled for the signed-in publisher and for browsers signaling Do Not Track or Global Privacy Control.

The approved Plausible plan retains analytics for up to five years. Our daily aggregate reports are retained for 13 months and omit location details. Community activity totals are calculated separately from the site’s records and are visible only to the publisher. Those reports do not include contribution text or account identifiers.

When connected, Search Console supplies aggregate Google search-discovery information. It does not identify readers to this site. Measurements can be incomplete because of privacy settings, blocked requests, bots, or reporting delays; they do not establish who a visitor is or why they visited.

6. Education, not representation

This publication is independent of the government and military services. It is general education, not individualized legal advice or a promise of representation. Posting or receiving a reply does not create an attorney-client relationship.

Do not rely on a community response for a deadline, election of rights, or a specific legal decision. Consult qualified counsel who can review your facts and the current governing sources. This site does not currently accept legal clients.