Three Dollar Quill

Okay, let's see where my plans have ended up.

Because Artifact instances work by constructing a bespoke Matrix, it's not easy, but straightforward to handle encoding dependencies into an Input. One subtlety is that OutputFromInput is going to need to be passed an Input with depedency data, and that data needs to be correctly propagated. Or... hm. Either I allow arbitrary dependency association, or I do the injection implicitly, and have OutputFromInput specifically take... Ugh. It's actually kind of hard to confirm that a given Input actually "came from" a given Matrix. I think I can still do it, but it will be... fascinating.

Encoding Matrix dependencies on the Axes looks about as straightforward as I originally thought tracking them on Input would be, and handling the dependencies in the facts call should be no problem.

Now, let's see about moving some client code up to remove duplication. What I'm basically hoping to have work is, to create a wrapper around SelectionDirectory, which supplies values for the associated selections. Tracking these would require more Axes tweaks, but they would be pretty mild.

I was resting and planning all day, so I don't have time to put these into practice tonight, but I'm now reasonably confident that making the changes will work. First SelectionDirectory, then Input. Sadly, I think I won't actually need the context-variable rewrite, so I can/should hold off on that until I get more coverage.

Anyway, it's late and I should wind down.

Good night.