Thanks, that seems to work - not sure why the documentation says that you can put the policy under a routing instance.
I've applied the export policy in the base and can now see both next hops in the forwarding-table, but it doesn't show both routes as being 'selected' in the show route - is this behaviour correct/expected?
# show route forwarding-table family inet destination 10.195.254.141 table VRF
Routing table: VRF.inet
Internet:
Destination Type RtRef Next hop Type Index NhRef Netif
10.195.254.141/32 user 0 ulst 1048705 2
10.195.196.197 ucst 5960 2 ge-1/1/8.3180
10.195.206.206 ucst 6965 2 ge-1/1/8.3053
run show route table VRF 10.195.254.141 detail
VRF.inet.0: 1292 destinations, 3307 routes (1292 active, 0 holddown, 643 hidden)
10.195.254.141/32 (1 entry, 1 announced)
*OSPF Preference: 10
Next hop type: Router, Next hop index: 1048705
Address: 0x1ddfc2c8
Next-hop reference count: 2
Next hop: 10.195.196.197 via ge-1/1/8.3180, selected
Session Id: 0x1210
Next hop: 10.195.206.206 via ge-1/1/8.3053
Session Id: 0x1211
State: <Active Int>
Age: 1:31:19 Metric: 11
Validation State: unverified
Area: 81.4.0.0
Task: LCC-Corporate-OSPF
Announcement bits (2): 1-KRT 2-BGP_RT_Background
AS path: I
Communities: rte-type:81.4.0.0:1:0