Passer au contenu principal
Coquille premium v2Coquille responsive v4Parcours Québec d’abord en françaisRègle d’adhésion avec source françaiseSurface UI seulementAutorité détenue par l’APIAucune écriture fournisseurCentre de notifications v1
LangueFrançais
Plan de contrôle premium Bookwiser • exécution Québec/Canada
Menu actifPreuves
Coquille d’exécution du portail
Anonymous
Une coquille d’exécution Québec d’abord en français avec autorité bornée.
La coquille se lit maintenant comme une seule ligne de produit premium tout en portant le nouveau périmètre linguistique Québec/Canada : les parcours publics, commerciaux, d’onboarding et de contrats d’adhésion doivent adopter une posture d’abord en français au Québec, la présentation bilingue n’est acceptable que lorsque le français demeure au moins aussi visible, et les parcours d’adhésion ne doivent pas lier via une version non française tant que le parcours source en français n’a pas été fourni. La coquille préserve encore les lignes d’arrêt autour de la vérité d’authentification, des appels fournisseur, des opérations signées, des paiements, de la paie, des dépôts, des remises, de l’exécution en fiducie et des autres autorités réglementées.
Route d’atterrissage
Login
Présentation seulement. La vérité de route demeure gardée par la session et détenue par l’API.
Acteur actuel
Coquille non authentifiée
Aucun acteur n’est actuellement visible dans la coquille du portail.
Posture linguistique
Les parcours publics et commerciaux du Québec sont d’abord en français
Le rendu bilingue demeure une trajectoire d’implémentation contrôlée seulement lorsque le français reste au moins aussi visible et complet sur le plan opérationnel.
Posture contractuelle
Source française avant parcours d’adhésion non français
La coquille peut prévisualiser les parcours d’engagement et de contrat, mais la validité linguistique du contrat demeure détenue par l’API et soumise à révision.
Posture de limite
Gérer l’argent sans toucher à l’argent
La gravité commerciale augmente sans élargir l’autorité financière, de dépôt, de paie ou d’exécution en fiducie.
Posture de session
anonymous
Anonymous
No authenticated actor is currently visible to the shell. Public-safe chrome is still allowed, but truth remains API-owned.
Recommended landing: Login
Ligne de limite
Lignes d’arrêt visibles
Présentation premium, autorité bornée
No active session is present. The portal shell can guide routing, but the API remains the auth authority.
Keyboard focus, reduced motion, responsive collapse, and French-first Québec launch copy are now treated as shell-contract duties, not page-by-page garnish.
Raccourcis du cockpit
8 raccourcis de route
Accès aux commandes
Une barre de raccourcis groupée garde l’accès aux routes moderne et cohérent. Elle demeure une surface de navigation seulement : aucune mutation de workflow, approbation, contrôle fournisseur ou autorité d’exécution réglementée n’est introduite dans le navigateur.
AudiencePreuves
8 raccourcis de route sont disponibles. Utilisez Tab pour parcourir les cartes de résultats.
Connexion
Entrée auth
Entrée d’authentification détenue par l’API vers les coquilles équipe et client.
/login
Accueil
Racine publique
Racine publique premium avec posture produit bornée, cadrage de lancement juridiquement sûr et accès à l’OS Bookwiser complet.
/
À propos
Récit société
Histoire de l’entreprise, posture opérationnelle et cadre de gouvernance Canada d’abord.
/about
Espace client
Racine client
Hub d’espace client sécurisé pour la continuité du classeur, les téléversements, la révision et la préparation du dossier final.
/client
Dossier final
Couloir livraison
Couloir sécuritaire de livraison et de clôture du dossier final borné.
/client/final-package
Aide client
Aide client
Surface d’aide orientée client pour la continuité, le soutien de paquet et les prochaines étapes guidées.
/client/help
Révision
Couloir révision
Couloir de révision pour les paquets, échéanciers et prochaines actions pendant que l’autorité d’approbation demeure côté serveur.
/client/review
Téléversements
Couloir réception
Couloir de réception documentaire avec continuité sécuritaire des téléversements et sans autorité privilégiée de révision.
/client/uploads
La posture de recherche demeure volontairement bornée à la clarté de navigation. La vérité de route, de session et d’autorité d’exécution demeure côté API.
Exécution de présentation
Bookwiser Default

Navy, gold, and high-trust contrast for premium control-plane posture.

Light shell
Premium shell coverage
Public and flagship shell • Staff and operator shell • Client-safe shell • Proof and screenshot discipline
Reduced motion is honored automatically when the device preference requests it, so flagship and commercial captures remain calm.
Architecture des routes
4 couloirs groupés
Architecture de l’information
La navigation groupée rend l’étendue lisible : onboarding, continuité client, commande équipe et couloirs preuve/lancement se lisent comme un seul cockpit plutôt qu’une liste de routes dispersée.
Entrée publique
Entonnoir public et posture de lancement
Garder le positionnement public, l’aide, la tarification et les parcours de lancement dans une seule taxonomie calme afin que la langue, la posture juridique et le cadrage commercial restent cohérents.
AccueilRacine publique
Racine publique premium avec posture produit bornée, cadrage de lancement juridiquement sûr et accès à l’OS Bookwiser complet.
/
PlateformeRécit plateforme
Récit unifié de la plateforme pour la comptabilité, l’ERP, la paie, le CRM, le social et les îlots d’exécution bornés.
/platform
IndustriesParcours sectoriels
Parcours verticaux phares pour le droit, le commerce de détail, les services professionnels et les autres couloirs de révision bornée.
/industries
TarificationParcours commercial
Packaging commercial borné par la révision, offres cadrées et étiquettes de certification sûres pour la feuille de route.
/pricing
À proposRécit société
Histoire de l’entreprise, posture opérationnelle et cadre de gouvernance Canada d’abord.
/about
ContactParcours contact
Surface de contact et de transfert d’entonnoir bilingue sans impasse linguistique.
/contact
AideCentre d’aide
Centre d’aide géré qui garde les parcours d’accompagnement, de FAQ et de soutien borné visibles depuis chaque coquille.
/help
ConnexionEntrée auth
Entrée d’authentification détenue par l’API vers les coquilles équipe et client.
/login
CommencerParcours lancement
Parcours de lancement Québec d’abord en français, cadrage d’engagement et onboarding guidé sans autorité commerciale détenue par le navigateur.
/get-started
Centre juridiqueRegistre des politiques
Registre versionné des politiques et surfaces d’acceptation auditables avec posture juridique Québec d’abord en français.
/legal
Continuité client
Classeur, téléversements, révision et dossier final
Transformer le parcours client en un seul couloir visible de continuité plutôt qu’en surfaces dispersées de documents, d’aide et de paquets.
Espace clientRacine client
Hub d’espace client sécurisé pour la continuité du classeur, les téléversements, la révision et la préparation du dossier final.
/client
Aide clientAide client
Surface d’aide orientée client pour la continuité, le soutien de paquet et les prochaines étapes guidées.
/client/help
ClasseurCouloir classeur
Couloir de continuité du classeur avec posture structurée de paquet et de livrable.
/client/workbook
TéléversementsCouloir réception
Couloir de réception documentaire avec continuité sécuritaire des téléversements et sans autorité privilégiée de révision.
/client/uploads
RévisionCouloir révision
Couloir de révision pour les paquets, échéanciers et prochaines actions pendant que l’autorité d’approbation demeure côté serveur.
/client/review
Dossier finalCouloir livraison
Couloir sécuritaire de livraison et de clôture du dossier final borné.
/client/final-package
Commande équipe
Opérations, conformité, finance et démonstrations phares
Regrouper le plan de contrôle opérateur par enjeu afin que les couloirs d’exécution, de tâches, d’audit, de confidentialité, de finance et de démonstration se lisent comme un seul système de commande.
Accueil équipeTour de contrôle
Surface d’atterrissage de tour de contrôle pour les signaux d’exécution, la navigation adaptée au rôle et la posture opérationnelle.
/staff
TâchesCouloir ops
Couloir borné de tâches pour l’assignation, le suivi et la visibilité des files.
/staff/tasks
ÉtatÉtat exécution
Visibilité d’exécution et des blocages pour le lancement géré et les opérations quotidiennes.
/staff/status
SantéCouloir sondes
Couloir d’environnement et de sondes pour la confiance d’exécution opérée.
/staff/health
AuditCouloir preuves
Couloir de preuve et d’inspection pour les révisions compatibles audit et les traces bornées.
/staff/audit
ConfidentialitéCouloir confidentialité
Surface d’opérations de confidentialité pour les incidents, demandes, rétention et posture de gouvernance.
/staff/privacy
QBOCouloir finance
Surface comptable et financière sûre en lecture pour la révision connexe aux livres.
/staff/qbo
CommercialCouloir commercial
Couloir interne de packaging commercial, devis, launchpack, renouvellement et traitement des objections.
/staff/commercial
PortefeuilleCouloir portefeuille
Visibilité portefeuille des clients et services pour une continuité commerciale gérée.
/staff/portfolio
Direction et développement
Gouvernance, preuves et surfaces de contrôle plateforme
Garder les surfaces de gouvernance, de lancement, de preuve et de développement visibles dans la même taxonomie plutôt que dans des chemins secondaires cachés.
DirectionCockpit direction
Cockpit de direction pour le lancement, la gouvernance, l’autorité et la posture inter-entités.
/staff/executive
DéveloppementCouloir dev
Couloir développement et exécution pour les preuves, contrôles et l’inspection de la plateforme.
/staff/dev
PreuvesCockpit preuves
Cockpit de preuves pour l’évidence gérée, la répétition de prévisualisation et les routes sûres pour capture d’écran.
/proofs
Preuve niveau concurrentPreuve phare
Couloir de preuve phare pour l’évidence premium de portée actuelle et la discipline de démonstration.
/proofs/competitor-grade
Preuve opérations liveOpérations live
Couloir de preuve opérationnelle pour les démonstrations live-ops sans revendications d’exécution.
/proofs/live-ops
Historique des preuvesCouloir historique
Couloir d’historique des preuves et d’inspection des runs avec posture preuve seulement.
/proofs/history
Préparation au lancementCouloir lancement
Blocages de lancement, posture de préparation et visibilité de publication compatible certification.
/staff/launch-readiness
Carte des routes de démonstration
3 séquences cartographiées
Routes de démonstration sélectionnées
Chaque capacité phare repose maintenant sur une séquence nommée : pitch public, continuité client/aide et démonstrations équipe restent alignés sans dépendre de liens cachés ou de la mémoire du présentateur.
Parcours de pitch public
Un parcours de pitch borné de l’entrée publique aux couloirs phares
Utiliser une séquence stable pour les démos et parcours : positionnement public, tarification, lancement, aide, continuité client et routes phares équipe.
1Accueil
Racine publique
Racine publique premium avec posture produit bornée, cadrage de lancement juridiquement sûr et accès à l’OS Bookwiser complet.
/
2Tarification
Parcours commercial
Packaging commercial borné par la révision, offres cadrées et étiquettes de certification sûres pour la feuille de route.
/pricing
3Commencer
Parcours lancement
Parcours de lancement Québec d’abord en français, cadrage d’engagement et onboarding guidé sans autorité commerciale détenue par le navigateur.
/get-started
4Aide
Centre d’aide
Centre d’aide géré qui garde les parcours d’accompagnement, de FAQ et de soutien borné visibles depuis chaque coquille.
/help
5Espace client
Racine client
Hub d’espace client sécurisé pour la continuité du classeur, les téléversements, la révision et la préparation du dossier final.
/client
6Commercial
Couloir commercial
Couloir interne de packaging commercial, devis, launchpack, renouvellement et traitement des objections.
/staff/commercial
7QBO
Couloir finance
Surface comptable et financière sûre en lecture pour la révision connexe aux livres.
/staff/qbo
8Préparation au lancement
Couloir lancement
Blocages de lancement, posture de préparation et visibilité de publication compatible certification.
/staff/launch-readiness
Parcours phare équipe
Un parcours équipe pour l’étendue et la confiance
Garder les démos opérateur cohérentes avec une seule séquence équipe qui se termine sur la posture de lancement et de gouvernance.
1Accueil équipe
Tour de contrôle
Surface d’atterrissage de tour de contrôle pour les signaux d’exécution, la navigation adaptée au rôle et la posture opérationnelle.
/staff
2Tâches
Couloir ops
Couloir borné de tâches pour l’assignation, le suivi et la visibilité des files.
/staff/tasks
3État
État exécution
Visibilité d’exécution et des blocages pour le lancement géré et les opérations quotidiennes.
/staff/status
4Audit
Couloir preuves
Couloir de preuve et d’inspection pour les révisions compatibles audit et les traces bornées.
/staff/audit
5Confidentialité
Couloir confidentialité
Surface d’opérations de confidentialité pour les incidents, demandes, rétention et posture de gouvernance.
/staff/privacy
6Commercial
Couloir commercial
Couloir interne de packaging commercial, devis, launchpack, renouvellement et traitement des objections.
/staff/commercial
7Direction
Cockpit direction
Cockpit de direction pour le lancement, la gouvernance, l’autorité et la posture inter-entités.
/staff/executive
8Préparation au lancement
Couloir lancement
Blocages de lancement, posture de préparation et visibilité de publication compatible certification.
/staff/launch-readiness
Parcours de continuité client
Une seule séquence calme de continuité pour le travail client
Montrer l’aide, le classeur, les téléversements, la révision et le dossier final comme un seul parcours client lisible.
1Espace client
Racine client
Hub d’espace client sécurisé pour la continuité du classeur, les téléversements, la révision et la préparation du dossier final.
/client
2Aide client
Aide client
Surface d’aide orientée client pour la continuité, le soutien de paquet et les prochaines étapes guidées.
/client/help
3Aide
Centre d’aide
Centre d’aide géré qui garde les parcours d’accompagnement, de FAQ et de soutien borné visibles depuis chaque coquille.
/help
4Classeur
Couloir classeur
Couloir de continuité du classeur avec posture structurée de paquet et de livrable.
/client/workbook
5Téléversements
Couloir réception
Couloir de réception documentaire avec continuité sécuritaire des téléversements et sans autorité privilégiée de révision.
/client/uploads
6Révision
Couloir révision
Couloir de révision pour les paquets, échéanciers et prochaines actions pendant que l’autorité d’approbation demeure côté serveur.
/client/review
7Dossier final
Couloir livraison
Couloir sécuritaire de livraison et de clôture du dossier final borné.
/client/final-package
La carte demeure présentation seulement. L’atteignabilité des routes est plus claire ici, mais les permissions, appels fournisseur, approbations et exécutions réglementées demeurent côté API.
Notifications de coquille

Session, routing, and boundary posture stay visible before you enter a lane.

The shell now keeps the most important runtime reminders together: session posture, recommended landing, French-first Québec launch rules, and mobile-safe continuity cues stay visible without turning the browser into an authority surface.

4 in view
Runtime notification
Public-safe
La coquille publique sécuritaire demeure visible
The shell is still allowed to render a calm public-safe runtime while authentication remains unresolved. Route, auth, and authority truth stay server-owned.
Runtime notification
4 lanes visible
Recommended landing remains explicit
Login is the current shell landing posture. The mobile shell keeps route intent visible without inventing browser-owned access or redirect truth.
Runtime notification
Québec path guarded
French-first Québec launch rules stay attached to the shell
Public, commercial, onboarding, and standard-form contract lanes continue to carry French-first posture. Bilingual presentation remains controlled and only acceptable where French stays at least as prominent and operationally complete.
Runtime notification
Premium shell polish
Mobile parity and notification posture are now first-class shell duties
Safe-area padding, calm collapse rules, shell notifications, and clearer board/card grouping now travel with the layout instead of depending on page-by-page polish.
Aperçu de connexion + preuve des gardes de route
Logged-out, staff, and client route visibility stays fail closed.
Wrong-role routes fail closed and public/help roots remain visible without moving authority into the browser. Demo-critical login transitions remain explicit and wrong-role routes redirect back to the session-owned landing route instead of exposing hidden access.
Current session scenario
Current posture
Logged-out portal posture
Logged-out requests to staff or client headline routes redirect to /login with login_required. Public/help roots remain reachable without manufacturing authenticated workspace access.
2 visible5 redirected0 wrong-role fail-closed
Staff executiveRedirects to /login (Redirects to login when there is no active authenticated session.)
Client executiveRedirects to /login (Redirects to login when there is no active authenticated session.)
Client action packRedirects to /login (Redirects to login when there is no active authenticated session.)
Preview guard scenario
Preview posture
Authenticated staff posture
Visiting /login while already authenticated as staff redirects to /staff/executive. Visiting a client-only headline route redirects back to the staff landing route with client_workspace_required.
3 visible4 redirected3 wrong-role fail-closed
Staff executiveVisible (This route is allowed for the current portal session snapshot.)
Client executiveRedirects to /staff/executive (Redirects away because the session does not have client workspace visibility.)
Client action packRedirects to /staff/executive (Redirects away because the session does not have client workspace visibility.)
Preview guard scenario
Preview posture
Authenticated client posture
Visiting /login while already authenticated as client redirects to /client/executive. Visiting a staff-only headline route redirects back to the client landing route with staff_workspace_required.
4 visible3 redirected2 wrong-role fail-closed
Staff executiveRedirects to /client/executive (Redirects away because the session does not have staff workspace visibility.)
Client executiveVisible (This route is allowed for the current portal session snapshot.)
Client action packVisible (This route is allowed for the current portal session snapshot.)
Surfaces d’entrée
Un seul cockpit, groupé par posture premium de couloir et règles de lancement d’abord en français.
Every top-level route card now uses the same shell grammar: lane accent, bounded copy, consistent hierarchy, French-first Québec launch posture for public/commercial paths, and a clear destination line without inventing browser-owned route authority.
Bookwiser proofs
fail posture
Bookwiser • Preuves • Competitor Grade
Screenshot-safe flagship proof surface for closeout posture, browser-lane evidence review, external packet families, and truthful stop-line visibility.
Posture de limite
Coquille premium, autorite bornee
Le portail peut afficher une posture d'execution bornee, mais les approbations, appels fournisseur, ecritures, depots, remises, mouvements de fonds et executions reglementees demeurent cote API.
Signal de commande
Blocker-closeout readiness
Stop-line visible
not ready
This measures whether the blocker-closeout bundle is structured cleanly enough to feed a truthful re-gate packet. It is not a widening authorization signal.
Signal de commande
Browser-lane intake
Stop-line visible
not_requested
The current-scope gate only re-enters on browser evidence when external-browser-evidence-verifier.json returns accept.
Signal de commande
Browser-lane execution mode
Stop-line visible
embedded rerun
Gate runner requested browser-compatible rerun packets using no local browser detected.
Signal de commande
Dependency/runtime lane
Stop-line visible
blocked
The current-scope gate now records the standard host dependency/runtime lane directly from the installed-browser proof packet.
Decision packet
stop blocker closeout required
Final decision: stop_blocker_closeout_required. Scope widening remains blocked because dependency_runtime=blocked, cleanup=blocked, docker_runtime=blocked, browser_lane_gate_intake=not_requested, hosted_workflow=blocked, email_provider_sandbox=external_capture_required, ….
Evaluated Apr 13, 2026, 10:05 a.m. • current_scope_competitor_grade_gate_v3
  • dependency_runtime=blocked
  • cleanup=blocked
  • docker_runtime=blocked
  • browser_lane_gate_intake=not_requested
  • hosted_workflow=blocked
  • email_provider_sandbox=external_capture_required
  • qbo_sandbox=external_capture_required
  • route_registry_closeout=fail
  • installed_browser_proof=fail
  • managed_stack_browser_proof=fail
  • container_runtime_proof=partial
  • hosted_workflow_hardening=fail
  • email_live_capture_packet=partial
  • qbo_live_capture_packet=partial
Do not widen scope. Fix the failed foundational proof surfaces first, then re-run this gate from a fresh blocker-closeout snapshot.
Plan des routes
Restez dans un seul cockpit calme et coherent.
Menu actifPreuves
Surface UI/application seulement
MenuPreuves
Readiness strip
Closeout readiness
These proof-strip signals keep the most important stop-lines, browser-family intake posture, and external evidence expectations readable at screenshot scale.
Control
Gate posture
FAIL
34
%
Final decision: stop_blocker_closeout_required. Scope widening remains blocked because dependency_runtime=blocked, cleanup=blocked, docker_runtime=blocked, browser_lane_gate_intake=not_requested, hosted_workflow=blocked, email_provider_sandbox=external_capture_required, ….
Control
Browser intake
not requested
0
%
Browser-lane gate intake could not consume external-browser-evidence-verifier.json because one or both rerun packet roots are missing.
Control
Blocker closeout
not ready for regate input
46
%
The blocker-closeout bundle is not yet ready for truthful re-gate input because one or more classification or packet-governance prerequisites are still missing.
Control
External evidence
Packet-tracked
0
%
4 packet families tracked on this proof surface.
Trust signals
Proof pages now surface trust and stop-lines directly.
That keeps the flagship proof page modern and presentation-safe while still communicating exactly how far the current evidence really goes.
Canada-first runtime
AWS ca-central-1 production path
Shipped
The launch story stays anchored to a Canada-first AWS posture so hosted trust cues in-product match the active launch packet.
Canada data path
Review-bounded control
Audit-grade evidence above execution systems
Shipped
Bookwiser coordinates packets, approvals, evidence, and follow-through without pretending the browser owns filing, payroll submission, money movement, or trust execution.
Bounded authority
Competitor gap closure
Breadth work is real, but still incomplete
Partial
Bank-connect, Quebec depth, mobile polish, AI data-entry, and reporting are now governed as explicit expansion lanes instead of implied completeness.
Governed modernization
Certification ladder
Regulated execution remains gated
Coming Soon - Certification Needed
Formal filing, payroll submission, money movement, and similar regulated lanes stay outside the product until legal or certification posture changes.
No hidden authority
Proof status model
This flagship surface now explains quality, gaps, and stop-lines in one language.
The result is easier to trust than a page that looks premium but hides its real blocker posture.
Proof surface quality
Shipped
The proof experience is now polished enough to support sales, walkthroughs, and screenshots without reading like a raw debug dump.
Modernized flagship page
Visible in-product and already supportable within the current bounded runtime.
Hosted and browser evidence completeness
Partial
Evidence review is real and structured, but it can still return partial posture until artifacts and secrets are complete.
Current gate outcome
Real and progressing, but still incomplete enough that UI and commercial copy must stay explicit.
Regulated execution interpretation
Coming Soon - Certification Needed
The page can explain proof and readiness, but it still cannot be used to imply authority beyond the bounded runtime.
Interpret carefully
Roadmapped intentionally, but blocked on licensing, regulated partner infrastructure, or formal certification.
Silent proof promotion
Forbidden
No beautiful proof page should ever blur blocker posture into live-provider authority or automatic hosted readiness.
Stop-line preserved
Must not be implied or relabeled as shipped under the current truth contract.
Proof priorities

Start with the gate decision, browser intake, and blocker closeout.

This gives the page a clearer executive read before the deeper packet cards, evidence families, and tables begin.

Gate posturefail

Final decision: stop_blocker_closeout_required. Scope widening remains blocked because dependency_runtime=blocked, cleanup=blocked, docker_runtime=blocked, browser_lane_gate_intake=not_requested, hosted_workflow=blocked, email_provider_sandbox=external_capture_required, ….

stop blocker closeout required
Browser intakenot requested

Browser-lane gate intake could not consume external-browser-evidence-verifier.json because one or both rerun packet roots are missing.

not requested
Blocker closeoutnot ready for regate input

The blocker-closeout bundle is not yet ready for truthful re-gate input because one or more classification or packet-governance prerequisites are still missing.

49 blocker(s) currently surfaced
External packet families0 clear

4 packet families are tracked on this proof surface.

Packet-tracked review posture
Closeout export
Review/export only
Compact closeout export packet
Compact browser closeout export packet for installed-browser and managed-stack rerun families. Use it as a review/export handoff only; it is not a pass or scope-unlock signal.
Packet signal
Compact closeout export packet
Review/export only
not ready for regate input
Compact browser closeout export packet for installed-browser and managed-stack rerun families. Use it as a review/export handoff only; it is not a pass or scope-unlock signal.
installed root: missingmanaged root: missingartifact: /tmp/bookwiser-current-scope-LRHcuy/browser-closeout-export-packet.json
Bounded execution island
Execution island state
Boundary posture
Use this single artifact to hand off per-family blocker manifests and closeout task lists for the next external rerun without reading the full gate packet.
Handoff receipt
Non-authorizing
Pre-rerun completeness receipt
Pre-rerun completeness receipt for the compact browser closeout export. Use it to confirm both packet families, blocker counts, task counts, and handoff completeness before the next external rerun.
Packet signal
Pre-rerun completeness receipt
Non-authorizing
2 blockers tracked
Pre-rerun completeness receipt for the compact browser closeout export. Use it to confirm both packet families, blocker counts, task counts, and handoff completeness before the next external rerun.
installed tasks: 1managed tasks: 1packet roots complete: no
Bounded execution island
Execution island state
Boundary posture
This receipt confirms completeness posture before the next external rerun. It is evidence only and does not authorize proof promotion.
Rerun template
Submission guidance
Normalized rerun return template
Normalized post-rerun submission template for installed-browser and managed-stack browser families. Use it as rerun submission guidance only so the next external browser packet comes back in one machine-comparable shape.
Packet signal
Normalized rerun return template
Submission guidance
5 common fields
Normalized post-rerun submission template for installed-browser and managed-stack browser families. Use it as rerun submission guidance only so the next external browser packet comes back in one machine-comparable shape.
installed required artifacts: 4managed required artifacts: 4artifact: /tmp/bookwiser-current-scope-LRHcuy/browser-rerun-return-template.json
Bounded execution island
Execution island state
Boundary posture
This template standardizes the next external rerun handoff. It does not create a pass signal or start proof execution from the browser.
Re-gate entry
Entry-readiness evidence
Truthful re-gate entry packet
The browser re-gate entry packet packages the input receipt, review packet, return receipt, and current browser-lane intake into one non-authorizing entry artifact, but structural readiness for truthful re-gate is still incomplete.
Packet signal
Truthful re-gate entry packet
Entry-readiness evidence
not ready for truthful regate
The browser re-gate entry packet packages the input receipt, review packet, return receipt, and current browser-lane intake into one non-authorizing entry artifact, but structural readiness for truthful re-gate is still incomplete.
receipt validation: submission_not_suppliedintake mode: not requestedartifact: /tmp/bookwiser-current-scope-LRHcuy/browser-regate-entry-packet.json
Bounded execution island
Execution island state
Boundary posture
This packet may show that the structure is ready for a truthful re-gate. It still does not authorize hosted promotion, provider contact, or browser-owned proof control.
Gate checks
Flagship check stack
The core competitor-grade checks now render like collateral instead of a debug page while keeping stop-lines explicit.
Gate check
pass
Workspace runtime normalization
The normalized npm workspace contract executed cleanly and reported deterministic package-manager, lockfile, and path-alias posture.
  • exitCode=0
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
fail
Route registry and module-resolution closeout
The route-registry closeout proof did not execute cleanly.
  • exitCode=1
  • node:internal/modules/esm/resolve:275
  • throw new ERR_MODULE_NOT_FOUND(
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
fail
Installed browser harness proof
Standard host dependency/runtime preflight is still blocked, so installed-browser execution on the standard runtime is not yet proven.
  • exitCode=0
  • status=fail
  • proofArtifactRoot=/tmp/bookwiser-current-scope-LRHcuy/checks/portal-install-proof
  • browserRerunStatus=blocked
  • dependencyRuntimeLane=blocked
  • standardRuntimeVerdict=runtime_blocked
  • browserExecutionDisposition=runtime_blocked
  • browserPolicyLane=clear
  • dependencyRuntime:Portal browser-runtime preflight exited with 1.
  • dependencyRuntime:Managed portal runtime did not start cleanly for installed-browser proof.
  • Portal browser contract surfaces: pass
  • Logged-out, staff, and client route visibility: pass
  • Portal install preflight: partial
  • Installed browser execution: fail
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
fail
Full managed-stack browser proof
API plus portal managed-stack startup, HTTP reachability, browser rerun packet creation, and browser execution were re-evaluated as one local proof surface.
  • exitCode=0
  • status=fail
  • proofArtifactRoot=/tmp/bookwiser-current-scope-LRHcuy/checks/portal-e2e-proof
  • browserRerunStatus=blocked
  • Managed stack contract and install preflight: partial
  • Logged-out, staff, and client route visibility: pass
  • Managed local stack execution: partial
  • Managed runtime HTTP reachability: partial
  • Managed browser execution: fail
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
partial
Docker runtime render and container smoke
The container topology, preview/promotion contract rehearsal, compose render posture, and smoke posture were re-evaluated honestly.
  • exitCode=0
  • status=partial
  • proofArtifactRoot=/tmp/bookwiser-current-scope-LRHcuy/checks/runtime-container-proof
  • Declared runtime topology files: pass
  • Local standard portal runtime contract: pass
  • Preview/promotion container contract rehearsal: partial
  • Docker CLI availability: partial
  • Compose render: partial
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
fail
Hosted workflow dispatch hardening
One or more hosted workflow hardening surfaces are missing, so the gate cannot rely on the hosted artifact contract.
  • .github/workflows/ci.yml: missing
  • .github/workflows/e2e.yml: missing
  • .github/workflows/release-gate.yml: missing
  • apps/bookwiser-api/src/proofs/market-hardening-proof-runner.ts: present
  • docs/ops/github-dispatch-ops-v1.md: present
  • docs/gates/hosted-artifact-matrix-v1.md: present
  • missing=.github/workflows/ci.yml
  • missing=.github/workflows/e2e.yml
  • missing=.github/workflows/release-gate.yml
  • hostedExecution=in_chat_not_performed
  • packetDriven=true
  • packetChecklist=docs/gates/hosted-artifact-matrix-v1.md
  • liveHostedExecutionClaimed=false
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
partial
Email sandbox live-capture packet
Email sandbox capture surfaces remain present and server-owned. Live provider traffic is still an external packet-driven evidence requirement.
  • apps/bookwiser-api/src/notifications/email-provider.ts: present
  • apps/bookwiser-api/src/notifications/provider-adapters/resend-provider.ts: present
  • apps/bookwiser-api/src/notifications/provider-webhook.ts: present
  • apps/bookwiser-api/src/server/routes/reminder-routes.ts: present
  • apps/bookwiser-api/src/proofs/email-provider-sandbox-proof.ts: present
  • apps/bookwiser-portal/src/app/staff/reminders/review/page.tsx: present
  • docs/integrations/email-sandbox-live-capture-v1.md: present
  • docs/ops/provider-evidence-checklist-v1.md: present
  • liveEmailTraffic=in_chat_not_performed
  • packetDriven=true
  • packetChecklist=docs/ops/provider-evidence-checklist-v1.md
  • liveProviderTrafficClaimed=false
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Gate check
partial
QBO sandbox live-capture packet
QBO sandbox capture surfaces remain present and read-only. Live Intuit traffic is still an external packet-driven evidence requirement.
  • apps/bookwiser-api/src/qbo/webhook-handler.ts: present
  • apps/bookwiser-api/src/qbo/sync-job-service.ts: present
  • apps/bookwiser-api/src/jobs/qbo-sync-worker.ts: present
  • apps/bookwiser-api/src/server/routes/qbo-sync-routes.ts: present
  • apps/bookwiser-api/src/proofs/qbo-sandbox-proof.ts: present
  • apps/bookwiser-portal/src/app/staff/qbo/syncs/page.tsx: present
  • docs/integrations/qbo-live-capture-v1.md: present
  • docs/ops/qbo-evidence-checklist-v1.md: present
  • liveQboTraffic=in_chat_not_performed
  • qboMode=read_only
  • packetDriven=true
  • packetChecklist=docs/ops/qbo-evidence-checklist-v1.md
  • liveIntuitTrafficClaimed=false
This is review output only. Passing or partial review copy on this page does not unlock scope, provider execution, or browser-owned proof control.
Browser-lane intake
not requested
Installed-browser and managed-stack family review
Browser-lane gate intake could not consume external-browser-evidence-verifier.json because one or both rerun packet roots are missing.
Packet-family view of browser-lane artifact completeness, comparison coverage, closeout tasks, and path consistency.
FamilyIntakeArtifactsComparison fieldsCloseout tasksBrowser path
Installed browserinstalledBrowser rerun packet root was not supplied to the gate intake verifier.
not requested
0/0Complete artifact set
0No missing fields
1Deterministic closeout tasks remain for this browser family.
Needs reviewNo browser path recorded
Managed stackmanagedStack rerun packet root was not supplied to the gate intake verifier.
not requested
0/0Complete artifact set
0No missing fields
1Deterministic closeout tasks remain for this browser family.
Needs reviewNo browser path recorded
Verifier artifact: not supplied • request mode: not requested
Operational lanes
Underlying runtime and browser-policy lanes
These lanes keep dependency/runtime, browser policy, cleanup, and Docker posture legible without dropping into raw proof artifacts.
Lane posture
blocked
Dependency/runtime lane
Standard host runtime remains blocked at dependency/runtime preflight before a clean installed-browser execution could be proven.
  • preflightVerdict=runtime_blocked
  • executionDisposition=runtime_blocked
  • runtimeMode=standard
  • Portal browser-runtime preflight exited with 1.
  • Managed portal runtime did not start cleanly for installed-browser proof.
  • dependency_contract=clear
  • test_plan=clear
  • managed_preflight=clear
  • browser_runtime_preflight=blocked
  • proof_environment_lanes=blocked
  • managed_stack_start=not_run
  • portal_reachability=not_run
  • managed_stack_stop=not_run
  • browser_execution=not_run
Lane posture
clear
Browser-policy lane
Browser-policy blockers are clear in the current gate packet.
  • browserPolicyLane=clear
Lane posture
blocked
Cleanup lane
Cleanup evidence remains a separate blocker lane for browser reruns.
  • Installed-browser cleanup remains a blocker or is still unverified.
  • Managed-stack cleanup remains a blocker or is still unverified.
  • installedCleanupGate=unknown
  • installedCleanupAcceptable=unknown
  • managedCleanupGate=unknown
  • managedCleanupAcceptable=unknown
Lane posture
blocked
Docker/runtime lane
Docker/runtime blockers remain isolated from dependency/runtime, browser-policy, and cleanup blockers.
  • Preview/promotion rehearsal: Docker CLI is not installed or not executable in this environment.
  • Preview/promotion rehearsal: Docker Compose is not available in this environment.
  • Docker CLI is not installed or not executable in this environment.
  • Docker Compose is not available in this environment.
External packet families
Hosted and provider-adjacent evidence families
These families remain explicit and bounded so the flagship gate never over-claims hosted or provider completion.
Packet-driven family
blocked
Docker/runtime external evidence family
Docker/runtime remains packetized but blocked here; topology and render posture were captured without claiming daemon-backed completion in chat.
  • artifactPath=/tmp/bookwiser-current-scope-LRHcuy/checks/runtime-container-proof/external-evidence-posture.json
  • composeRunner=unavailable
  • dockerCli=missing
  • dockerDaemon=unreachable
  • containerSmoke=not_executed
  • liveExecutionClaimed=false
  • packetDriven=true
Checklist
Checklist path
docs/gates/current-scope-competitor-grade-gate-v3.md
The checklist remains the authoritative packet/review anchor for this external evidence family.
Artifact
Artifact path
/tmp/bookwiser-current-scope-LRHcuy/checks/runtime-container-proof/external-evidence-posture.json
Artifact references remain descriptive only and do not imply a hosted provider action was executed.
This family remains packet-driven or externally captured; it is not widened into browser-owned execution.
Packet-driven family
blocked
Hosted workflow external evidence family
Hosted workflow evidence stays external and packet-driven. This Docker/runtime proof does not claim hosted CI/E2E/release execution.
  • .github/workflows/ci.yml: missing
  • .github/workflows/e2e.yml: missing
  • .github/workflows/release-gate.yml: missing
  • apps/bookwiser-api/src/proofs/market-hardening-proof-runner.ts: present
  • docs/ops/github-dispatch-ops-v1.md: present
  • docs/gates/hosted-artifact-matrix-v1.md: present
  • missing=.github/workflows/ci.yml
  • missing=.github/workflows/e2e.yml
  • missing=.github/workflows/release-gate.yml
  • hostedExecution=in_chat_not_performed
  • packetDriven=true
  • packetChecklist=docs/gates/hosted-artifact-matrix-v1.md
  • liveHostedExecutionClaimed=false
  • liveExecutionClaimed=false
Checklist
Checklist path
docs/gates/hosted-artifact-matrix-v1.md
The checklist remains the authoritative packet/review anchor for this external evidence family.
Artifact
Artifact path
not captured
Artifact references remain descriptive only and do not imply a hosted provider action was executed.
This family remains packet-driven or externally captured; it is not widened into browser-owned execution.
Packet-driven family
external capture required
Email sandbox external evidence family
Email sandbox evidence stays external and packet-driven. This proof does not claim live provider traffic or inbox delivery.
  • apps/bookwiser-api/src/notifications/email-provider.ts: present
  • apps/bookwiser-api/src/notifications/provider-adapters/resend-provider.ts: present
  • apps/bookwiser-api/src/notifications/provider-webhook.ts: present
  • apps/bookwiser-api/src/server/routes/reminder-routes.ts: present
  • apps/bookwiser-api/src/proofs/email-provider-sandbox-proof.ts: present
  • apps/bookwiser-portal/src/app/staff/reminders/review/page.tsx: present
  • docs/integrations/email-sandbox-live-capture-v1.md: present
  • docs/ops/provider-evidence-checklist-v1.md: present
  • liveEmailTraffic=in_chat_not_performed
  • packetDriven=true
  • packetChecklist=docs/ops/provider-evidence-checklist-v1.md
  • liveProviderTrafficClaimed=false
  • liveExecutionClaimed=false
Checklist
Checklist path
docs/ops/provider-evidence-checklist-v1.md
The checklist remains the authoritative packet/review anchor for this external evidence family.
Artifact
Artifact path
not captured
Artifact references remain descriptive only and do not imply a hosted provider action was executed.
This family remains packet-driven or externally captured; it is not widened into browser-owned execution.
Packet-driven family
external capture required
QBO sandbox external evidence family
QBO sandbox evidence stays external and packet-driven. This proof does not claim live Intuit traffic or write-back completion.
  • apps/bookwiser-api/src/qbo/webhook-handler.ts: present
  • apps/bookwiser-api/src/qbo/sync-job-service.ts: present
  • apps/bookwiser-api/src/jobs/qbo-sync-worker.ts: present
  • apps/bookwiser-api/src/server/routes/qbo-sync-routes.ts: present
  • apps/bookwiser-api/src/proofs/qbo-sandbox-proof.ts: present
  • apps/bookwiser-portal/src/app/staff/qbo/syncs/page.tsx: present
  • docs/integrations/qbo-live-capture-v1.md: present
  • docs/ops/qbo-evidence-checklist-v1.md: present
  • liveQboTraffic=in_chat_not_performed
  • qboMode=read_only
  • packetDriven=true
  • packetChecklist=docs/ops/qbo-evidence-checklist-v1.md
  • liveIntuitTrafficClaimed=false
  • liveExecutionClaimed=false
Checklist
Checklist path
docs/ops/qbo-evidence-checklist-v1.md
The checklist remains the authoritative packet/review anchor for this external evidence family.
Artifact
Artifact path
not captured
Artifact references remain descriptive only and do not imply a hosted provider action was executed.
This family remains packet-driven or externally captured; it is not widened into browser-owned execution.
Visible blockers
49 blockers
What still stops the gate
This list stays explicit on the polished proof page so a premium UI never flattens real blocker posture into fake readiness.
  • Route registry and module-resolution closeout: exitCode=1
  • Installed browser harness proof: status=fail
  • Installed browser harness proof: browserRerunStatus=blocked
  • Installed browser harness proof: dependencyRuntimeLane=blocked
  • Installed browser harness proof: standardRuntimeVerdict=runtime_blocked
  • Installed browser harness proof: browserExecutionDisposition=runtime_blocked
  • Installed browser harness proof: Portal install preflight: partial
  • Installed browser harness proof: Installed browser execution: fail
  • Full managed-stack browser proof: status=fail
  • Full managed-stack browser proof: browserRerunStatus=blocked
  • Full managed-stack browser proof: Managed stack contract and install preflight: partial
  • Full managed-stack browser proof: Managed local stack execution: partial
  • Full managed-stack browser proof: Managed runtime HTTP reachability: partial
  • Full managed-stack browser proof: Managed browser execution: fail
  • Docker runtime render and container smoke: status=partial
  • Docker runtime render and container smoke: Preview/promotion container contract rehearsal: partial
  • Docker runtime render and container smoke: Docker CLI availability: partial
  • Docker runtime render and container smoke: Compose render: partial
  • Hosted workflow dispatch hardening: .github/workflows/ci.yml: missing
  • Hosted workflow dispatch hardening: .github/workflows/e2e.yml: missing
  • Hosted workflow dispatch hardening: .github/workflows/release-gate.yml: missing
  • Hosted workflow dispatch hardening: missing=.github/workflows/ci.yml
  • Hosted workflow dispatch hardening: missing=.github/workflows/e2e.yml
  • Hosted workflow dispatch hardening: missing=.github/workflows/release-gate.yml
  • Browser-lane gate intake: External browser evidence verifier packet roots are incomplete.
  • Dependency/runtime lane: preflightVerdict=runtime_blocked
  • Dependency/runtime lane: executionDisposition=runtime_blocked
  • Dependency/runtime lane: runtimeMode=standard
  • Dependency/runtime lane: Portal browser-runtime preflight exited with 1.
  • Dependency/runtime lane: Managed portal runtime did not start cleanly for installed-browser proof.
  • Dependency/runtime lane: dependency_contract=clear
  • Dependency/runtime lane: test_plan=clear
  • Dependency/runtime lane: managed_preflight=clear
  • Dependency/runtime lane: browser_runtime_preflight=blocked
  • Dependency/runtime lane: proof_environment_lanes=blocked
  • Dependency/runtime lane: managed_stack_start=not_run
  • Dependency/runtime lane: portal_reachability=not_run
  • Dependency/runtime lane: managed_stack_stop=not_run
  • Dependency/runtime lane: browser_execution=not_run
  • Cleanup lane: Installed-browser cleanup remains a blocker or is still unverified.
  • Cleanup lane: Managed-stack cleanup remains a blocker or is still unverified.
  • Cleanup lane: installedCleanupGate=unknown
  • Cleanup lane: installedCleanupAcceptable=unknown
  • Cleanup lane: managedCleanupGate=unknown
  • Cleanup lane: managedCleanupAcceptable=unknown
  • Docker/runtime lane: Preview/promotion rehearsal: Docker CLI is not installed or not executable in this environment.
  • Docker/runtime lane: Preview/promotion rehearsal: Docker Compose is not available in this environment.
  • Docker/runtime lane: Docker CLI is not installed or not executable in this environment.
  • Docker/runtime lane: Docker Compose is not available in this environment.
Remaining limits
Non-claims still preserved
The proof page can look flagship-grade and still keep the runway honest about what remains outside scope.
  • Standard host dependency/runtime lane remains blocked or pending, so installed-browser proof is not yet honestly closed.
  • Installed browser execution is still not fully proven in this environment.
  • Managed local API plus portal browser proof is still incomplete, so the combined installed stack is not yet honestly closed.
  • Browser-lane gate intake remains blocked because external-browser-evidence-verifier.json has not returned status=accept.
  • Docker-backed compose render and container smoke remain incomplete in this chat environment because Docker CLI and daemon access are unavailable.
  • Hosted CI, E2E, release-gate, preview, and promotion execution were not exercised in-chat; only dispatch-ready artifact posture was proven.
  • Live provider and live Intuit sandbox traffic were not exercised in-chat; email and QBO rungs are operator-ready capture packets, not live hosted evidence.
  • Because this gate did not pass cleanly, vendors and expenses remain unauthorized. Stop and create a blocker-closeout plan instead of widening scope.
Evidence timeline
Boundary rules and operator briefing
The polished proof surface keeps boundary rules and operator notes attached so screenshots remain beautiful without mutating the truth contract.
Boundary rule

Rule 1

non-authorizing

Wix remains marketing-only.

Boundary copy remains API-authored and does not widen provider, hosted, or browser execution authority.
Boundary rule

Rule 2

non-authorizing

Portal remains a UI/application-safe review surface only.

Boundary copy remains API-authored and does not widen provider, hosted, or browser execution authority.
Boundary rule

Rule 3

non-authorizing

API owns privileged workflow, provider, persistence, and QBO logic.

Boundary copy remains API-authored and does not widen provider, hosted, or browser execution authority.
Boundary rule

Rule 4

non-authorizing

QBO OAuth, verification, tokens, and sync logic remain server-side only and QBO stays read-only.

Boundary copy remains API-authored and does not widen provider, hosted, or browser execution authority.
Boundary rule

Rule 5

non-authorizing

No secrets or provider credentials move into browser-delivered code.

Boundary copy remains API-authored and does not widen provider, hosted, or browser execution authority.
Boundary rule

Rule 6

non-authorizing

Do not widen into vendors or expenses unless this gate passes cleanly.

Boundary copy remains API-authored and does not widen provider, hosted, or browser execution authority.
Operator note

Flagship note 1

operator guidance

Treat this page as a review surface only; all proof execution remains API-owned.

Operator guidance is review support only. It never becomes a pass signal, promotion signal, or browser-run proof action.
Operator note

Flagship note 2

operator guidance

Any non-pass result means vendors and expenses remain unauthorized in this runway.

Operator guidance is review support only. It never becomes a pass signal, promotion signal, or browser-run proof action.
Operator note

Flagship note 3

operator guidance

The current-scope gate now consumes external-browser-evidence-verifier.json explicitly and will not re-enter the browser lane unless that verifier returns accept.

Operator guidance is review support only. It never becomes a pass signal, promotion signal, or browser-run proof action.
Operator note

Flagship note 4

operator guidance

Per-family browser blocker manifests and closeout task lists are preserved in browser-lane-blocker-manifests.json and browser-lane-closeout-tasks.json so operators can follow packet-family-specific closeout work.

Operator guidance is review support only. It never becomes a pass signal, promotion signal, or browser-run proof action.
Les surfaces du portail Bookwiser resumment une posture d'execution detenue par l'API pour l'equipe et les clients. L'authentification privilegiee, les operations connecteurs, le controle QBO, les mutations de workflow et l'execution reglementee demeurent cote serveur.