Skip to main content

Blog

Field Notes & Updates

A living stream of Methods, Places, and community-led corrections--built for learning. We label what is supported, what is debated, and what is still being explored.

Browse the LibraryBrowse the WikiSubmit a Community Note

Note: This is an educational project. Posts may evolve as sources are added and claims are tightened.

What this stream adds

  • It shows how the project thinks in public when methods, place questions, or wording decisions change.
  • It gives readers a visible correction and update layer instead of hiding revision behind silent page edits.
  • It connects shorter field notes to the larger place hubs, source-review lanes, and editorial standards behind them.

How to use this stream

  • Use Methods posts when the question is how to compare sources, build a packet, or tighten public wording.
  • Use Places posts when the question needs a route, river, town, archive, cemetery, school, church, or public-site anchor.
  • Use Community Notes and Fact Checks when the issue is a disputed claim, correction request, source gap, or safer wording decision.
  • Use Project Updates when you need to understand what changed in the site itself before relying on an older page.

Do not use this stream to

  • Treat a short update as a final source packet.
  • Upgrade a method note into identity, ancestry, legal-status, DNA, descent, tribal, Nation, or membership proof.
  • Ignore a newer correction, evidence gate, or source-review page because an older post sounded more certain.

Partner learning path

Use both sites without collapsing their meanings

TheFoundationsOf.us focuses on foundations, Muur history, ancestral memory, place-based research, and community learning. MoorofUs.org provides evidence-first Moor history, people, places, timelines, claims, and sources. CultureUP.us carries broader culture and media coverage with visible source context.

What this partner path adds

  • It helps readers move between related projects without assuming they make the same kind of claim.
  • It reduces confusion by clarifying which site is best for foundations, which is best for wider Moor history, and which is best for broader cultural coverage.
  • It keeps the network useful by turning cross-site travel into a source-aware decision instead of a branding shortcut.

Cross-site evidence boundary

  • A link to a partner site is a reading route, not an endorsement that every claim on both pages has the same evidence level.
  • Do not move language from one site into another without preserving the source label, claim status, privacy limits, and date of the page being cited.
  • If a partner page changes the strength of a claim, treat the next step as source review or fact check rather than automatic republication.

Reader handoff output

You should leave knowing which site fits the question you actually have, what evidence boundary traveled with you, and what review lane is needed before cross-site language becomes public wording.

Explore Moor HistoryStudy the Wider LegacyCulture and Media ContextHow the sites connect

Use search when you already know part of the topic, place, or wording issue you are tracking and need the closest field note or archive entry quickly.

Featured Post

This spotlight marks a post that carries extra editorial weight right now, either because it adds a useful method, a stronger place reading, or a clearer review boundary.

Field Note

Abu Bakari and the Atlantic: What the Mali Sources Actually Say

A source-led flagship article on the Mali ruler often called Abu Bakari II, Mansa Musa's account to al-Umari, and why the Atlantic story deserves careful handling without turning memory into proof of American contact.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Why this entry matters now: it captures an active editorial question, place reading, or method problem before it hardens into a broader claim.

Atlantic MemoryClaim ReviewEvidence GatesMali EmpireSource Led HistoryAtlantic World

Evidence: Mixed: strong support for the reported Mali court story; no confirmed proof of an American landingStatus: Source-led, historically cautious, open to review

Start with a collection

These collection lanes separate different reading jobs so readers can choose research, narrative, place context, or method work without blending them together.

Methods

Build careful research habits.

Choose this lane when the main problem is how to read, compare, and label evidence more carefully.

Places

Follow rivers, paths, towns, and landscapes.

Choose this lane when geography, local records, routes, and institutions should shape the question first.

Original Thirteen Colonies

Compare colony source targets, readiness labels, and archive-first research lanes.

Choose this lane when the research job is colony-by-colony source acquisition, not a generic colonial-history summary.

Community Notes & Fact Checks

Read corrections and source-led challenges.

Choose this lane when a claim, wording choice, or source trail needs challenge, correction, or narrower public language.

Project Updates

See what changed and what is coming next.

Choose this lane when you need to see how the editorial surface, methods, or trust posture is changing over time.

Methods and Places

This split helps readers choose whether they need a research habit first or a place anchor first. Both lanes matter, but they answer different kinds of questions.

Methods

Use these posts when the main problem is how to read, compare, label, or narrow evidence before making a stronger claim.

Places

Use these posts when the main problem is place context, local records, landscape reading, or how a location changes the research question.

Help keep it accurate

Submit source-based context, corrections, and respectful questions so the project can improve over time. Please do not submit private information about living people. Use pseudonyms when helpful, redact sensitive details, and avoid publishing personal contact information.

This lane adds public accountability to the site: it gives readers a visible way to improve wording, sources, and context instead of leaving errors to linger silently.

Community NoteFact CheckSafe SharingCommunity Guidelines

Latest Posts

This stream shows the project thinking in public as methods, place questions, and review language evolve. Use it to spot where the editorial surface is changing most recently, not as a substitute for the deeper source packets.

Field Note

Apply Montezuma Continuity Fallback Wording Safely

A method post for using fallback wording when Montezuma continuity thresholds are not met.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Queue St. Augustine Alias Ambiguities for Review

A method post for queuing St. Augustine alias ambiguities before merge decisions.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Split Jacksonville Overbroad Claims Into Testable Units

A method post for decomposing broad Jacksonville claims into source-testable units.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Test Montezuma Continuity Threshold Before Publish

A method post for threshold-gating Montezuma continuity language before publication.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Log St. Augustine Merge Reversals Safely

A method post for documenting St. Augustine merge reversals and alias-risk notes.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Audit Jacksonville Evidence-Tier Changes

A method post for auditing Jacksonville tier moves before claim strengthening.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Track Montezuma Flood-to-Directory Deltas

A method post for delta-tracking across flood memory, depot routes, and directory updates.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Run a St. Augustine Translation Delta Audit

A method post for auditing translation deltas before merge status updates.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Build a Jacksonville Source Delta Ledger

A method post for turning Jacksonville claim edits into row-level delta logs.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Field Note

Attach Montezuma Correction Notes When Claim Status Changes

A method post for correction-note discipline when Montezuma claim statuses are updated.

Short editorial waypoint for method, place, or review thinking.

Next review step: Open the linked source, place, or review lane before treating this field note as settled.

Scroll to Top