Auditing and compliance is not the time to let nonsense slip through

Neither is 1am

Or is that

1am is not the time to be doing auditing and compliance nonsense

I can never remember how that goes

Anyhoo... little Ms 🪿 spent a long time building the blackout compare function just to ignore it completely and accept a hash from the user during verification

🪿 👀👀👀

Anyhoo... little Ms 🪿spent a little time wiring the blackout compare function to the document_verifier and now we properly track the hash of the document in the compliance update and compare to current on L0 rebuild

🛌🏻💤

#devops #devopsendgamewithallthecheatcodes #engineering #sneakygoose #thebreakroom

And that's that

Now if any part of the document changes, any prior approvals will become invalid at the prose level.

This means that individual fences (the functional building blocks of "middleware for your mind") are individually auditable and approved. This covers the case of a node coming out of superposition for execution.

We also track the overall hash of the document, including its approvals (with blacked out hashes providing stability). Any change to a runbook step, the description of a particular deployment pipeline or to an approval itself would trigger a reset of the entire document's approval status.

Neat

BRB

[rescuing Janet from the hypno-koala]

#devops #devopsendgamewithallthecheatcodes #engineering #isit #prettysurethisstillcounts #thebreakroom

This is why we test things.

We have individual fence plus document level approvals.

We've verified that fences invalidate automatically, now for the document.

... And of course they skipped a step. Trust but verify right 🪿

Won't be but a moment

#devops #devopsendgamewithallthecheatcodes #thebreakroom

We did fences, we need to verify the prose path.

Nothing fancy this time, just a run book

#devops #devopsendgamewithallthecheatcodes #thebreakroom

For those of you metaphorically challenged folk attempting to follow along at home, what this demonstrates is:

1. All documents in Wanderland are assigned provenance at birth. This means a virtual fence (structured text with an API) is injected into the bottom of the page when it is created which tracks the approval status for each fence , as well as the entire document as a whole.
2. Approvals are attached to a specific revision.
3. The same hash is calculated each time the document populates its L0 cache (ie. after each write). If any individual fence hash or the document hash changes and the associated approvals are reset
4. As the virtual fence (structured text with an API) is structured text with an API, we can query it. Any fence in an unapproved status with at least one changelog entry indicates a fence that was approved at one point that has been updated. This sounds like a dashboard...

#devops #devopsendgamewithallthecheatcodes #engineering #thebreakroom

Oh no Bob!

A missing salad and an experiment gone amok.

The drama continues in the Offices of Wanderland

#devops #devopsendgamewithallthecheatcodes #engineering #thebreakroom

This amuses me greatly

We have successfully created the breakroom-fridge-log and oh my goodness is Janet ever being a Janet

I've setup a scenario where a fictional breakroom log requires approval for each cleaning. Each cleaning update breaks the hash and resets the prior approval requiring re-approval from the breakroom supervisor

Poor Marcus gets caught in the middle it seems a bit of a spat... or does he?

#devops #devopsendgamewithallthecheatcodes #engineering #thebreakroom

The provenance system needs a bit more work before it's a fully operational battle station.

Each fence + the full document are hashed at L0 cache build (blackout hash algo for stability). Approvals automatically invalidated on content change, fence or document level.

So we need to test.

Anyone watch the office? (the funny one I mean)

#devops #devopsendgamewithallthecheatcodes #thebreakroom

#BreakingNews

#Marvel puso límites a la serie de #TuAmigoYVecinoSpiderMan!

En los últimos días, #MarvelStudios ha cerrado por todo lo alto la serie #YourFriendlyNeighborhoodSpiderMan. Aunque no comenzó con buen pie debido a su chocante animación, logró alcanzar el éxito con un final apoteósico. Al tratarse de un universo independiente del #UCM, los creadores tuvieron libertad para incluir a diversos personajes, aunque con algunas excepciones significativas.

A través de una entrevista con el programa #TheBreakroom, el showrunner de la serie #JeffTrammel reveló que Marvel Studios le prohibió añadir a #Los4Fantásticos y Gran Rueda, un villano de lo más estúpido y bizarro de la franquicia protagonizada por el trepamuros.

La prohibición de Los 4 Fantásticos se debe, principalmente, a que Marvel Studios planea reservar su presentación para la película que se estrenará en verano. En cuanto a Gran Rueda, no hay una explicación clara, pero los fans especulan que podría aparecer como estrella invitada en la cuarta entrega de Spider-Man en la gran pantalla.

Es poco probable que este villano sea el antagonista principal, ya que su rol en los cómics suele ser más humorístico que amenazante. Sin embargo, podría servir como hilo conductor en la historia de #SpiderMan4, facilitando la reintroducción de Peter Parker tras los acontecimientos de la tercera película, estrenada en 2021.