feat/tunnel modeling - #63
Conversation
|
Leaving here some links following our discussion. You will have to adjust the models to make use of the new What was already missing and needs to be added is support for your test inside of the To see how this is actually used, check the temporal activity: https://github.com/ooni/data/blob/main/oonipipeline/src/oonipipeline/temporal/activities/observations.py It's also worth reading the docs of temporal to understand what you should do and not do inside of an activity and workflow. If you want your tables to be created automatically via the Finally, you mentioned interest in making use of scheduled operations. You can see an example of how to set this up here: https://github.com/ooni/data/blob/main/oonipipeline/src/oonipipeline/temporal/workflows.py#L208, though note that this is currently not used in production and I haven't tested it heavily. |
b94f146 to
62d72d2
Compare
c9913a1 to
9edf29e
Compare
|
Do we still want to land something of this sort and run it? Ideally we would somehow make this converge together with: #48 |
Extends ontology, requirements, architecture, implementation-plan, and label-corpus-design with a tunnel observation tier (obs_tunnel, phase axis, provider/protocol targets, cross-network control), an external-report evidence class for corroboration only, and new M8/C9 requirements. Converges with #63; gated for rule weights until the corpus gains a screen_tunnel stratum (V2). produces through several iteration of AI assisted review and editing
work in progress; pushing for discussion on the data modelling and needed granularity.