You complete Matriarchy when the cards finish in the exact ordered tableau, run, or compressed layout required by this profile. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim.
Your unfinished game is saved only in this browser.
You complete Matriarchy when the cards finish in the exact ordered tableau, run, or compressed layout required by this profile. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim.
Complete guide
Matriarchy uses the independently implemented Matriarchy PySolFC 3.6.1 rules profile v1 profile (R398). Matriarchy is a complete deterministic browser game whose distinct rules centre on Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes.
Matriarchy opens from a versioned seeded position built for Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes. Its game ID, rules profile, and deal identity are stored together so restart recreates the same opening without a server request.
Every Matriarchy action is checked against the current board, available material, and this defining restriction: Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes. Invalid, stale, or post-terminal actions leave the position unchanged.
You complete Matriarchy when the cards finish in the exact ordered tableau, run, or compressed layout required by this profile. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim. Near the end of Matriarchy, recount the remaining obligations needed until the cards finish in the exact ordered tableau, run, or compressed layout required by this profile. Check the boundary rule after every final placement or transfer because terminal status is enforced immediately.
A practical Matriarchy plan is to preserve several legal continuations around Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes. Use the deterministic hint to inspect one legal action, then compare how it affects the documented objective before committing. A common Matriarchy error is to ignore the boundary rule that Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes. Undo is useful for studying that decision, while restart deliberately preserves the original seeded position.
Matriarchy has its own runtime and save identity because its rules require Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes.
Suit rows descend from Queens while paired King rows rise through Ace; talon packet size grows per pass and completed ranks earn descending bonus passes.
Matriarchy stores its game ID, rules version, and seeded deal identity. Those values recreate the same opening locally without promising that the position is forced or winnable.
