Roro
What it is
Section titled “What it is”Roro was a Robotic Process Automation (RPA) tool — software that records and replays sequences of user-interface actions across applications, used in business contexts to automate clerical workflows. The project is archived (no longer actively maintained), but the C# source is BSD-2-licensed and remains available. The README’s tagline (“To everyone, salamat sa pagsuporta” — “thanks for the support” in Tagalog) and the credit to Roslyn + Costura mark it as a one-person passion project that found its audience and reached its natural conclusion.
For KN-86 this is a light reference for the broader idea of scripted, recorded, replayable workflows — the kind of capability that pairs with the cart-Lisp scripting layer and the history.el navigation history to give the deck macro / scripted workflow capabilities akin to l123’s Alt-F5 LEARN mode or Emacs’s kmacro-start-macro.
Key takeaways for KN-86
Section titled “Key takeaways for KN-86”- Macro recording as a sanctioned cart-authoring affordance. The pattern: the user performs a sequence of actions; the runtime captures the sequence; the user names it; the named sequence is replayable as a single action. l123 does this with
Alt-F5 LEARN/Alt-F2 STEP/Alt-F3 RUN. KN-86 should commit to the same pattern on the REPL surface — a TERM-key verb that toggles record mode, a verb to name the recorded macro, a verb to invoke it. - RPA scope ≠ KN-86 scope. Roro is targeting business UI automation across multiple GUI applications. KN-86 is targeting a single device with a constrained input surface. The lesson here is structurally narrow: “record a sequence of actions, replay them” is a pattern that scales from “fill in a 30-field business form” down to “compose a five-step CIPHER-broadcast sequence.” Same pattern, different scale.
- C# / .NET / Roslyn is not the KN-86 stack. Reference only. No code adoption.
- Archived projects are still reference material. Roro is no longer maintained, but the BSD-2 source remains and the patterns inside it remain valid. KN-86 documentation should be comfortable citing archived projects — the lesson doesn’t expire when maintenance does.
License note
Section titled “License note”BSD 2-Clause. Genuinely permissive. KN-86 can read, reference, even port small code fragments if there’s ever cause. No copyleft propagation.
No image downloaded.
- Low-priority reference. Roro is included for completeness more than for direct influence — the macro-recording pattern is more cleanly addressed via l123 and Emacs
kmacro-*, both of which are more directly relevant to KN-86’s substrate. - Cross-link l123.md — the better, more directly relevant macro-recording reference.
- Cross-link history-el.md + xiki.md — together with macro recording, these three give the REPL surface a powerful scripted workflow story.
- Open question worth scoping: does the KN-86 macro system record at the keypress level (replay the literal keystrokes) or at the action / verb level (replay the named operations)? l123 records at the keystroke level. The action level is more robust against UI changes but requires the runtime to canonicalize user input into named actions before recording. Worth thinking about when the macro system gets a real spec.